Re: [Int-area] Fw: Continuing IPv10 I-D discussion.

2017-03-31 Thread Jen Linkova
t;>> the market had support for it. Probably 5-10 years after that before >>> support is widely available. >>> >>> IPv10 would delay and confuse deployment of something that is not IPv4. >>> While IPv6 is not perfect, there are now hundreds of millions of >&

Re: [Int-area] Fw: Continuing IPv10 I-D discussion.

2017-03-31 Thread Jen Linkova
rom: Lee Howard [mailto:l...@asgard.org] > Sent: Friday, March 31, 2017 5:35 PM > To: Khaled Omar; Jen Linkova > Cc: int-area@ietf.org > Subject: Re: [Int-area] Fw: Continuing IPv10 I-D discussion. > > > > On 3/31/17, 10:02 AM, "Int-area on behalf of Khaled Omar" >

[Int-area] Proposed Path Aware Networking RG Announcement

2017-07-12 Thread Jen Linkova
whether or not to charter it. Afterward, the RG intends to meet at 1-3 IETF meetings per year, and hold one workshop per year, collocated with a related academic conference. -- SY, Jen Linkova aka Furry ___ Int-area mailing list Int-area@ietf.org ht

[Int-area] Comment on draft-ietf-intarea-frag-fragile-02

2018-11-08 Thread Jen Linkova
s DNS servers. I apologia if it's been discussed before and rejected (I did not find such discussion on the list). -- SY, Jen Linkova aka Furry ___ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area

Re: [Int-area] Comment on draft-ietf-intarea-frag-fragile-02

2018-11-11 Thread Jen Linkova
I'm a bit confused. Which standard would need to be updated if the proposed recommendation is made? -- SY, Jen Linkova aka Furry ___ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area

Re: [Int-area] Comment on draft-ietf-intarea-frag-fragile-02

2018-11-12 Thread Jen Linkova
ionally*, it’s bad practice to indicate “SHOULD” unless the text > >> also explains why it isn’t a MUST, i.e., under what conditions it is OK to > >> not forward fragments. > > > > Sorry, I'm a bit confused. Which standard would need to be updated if

[Int-area] draft-augustyn-intarea-ipref: problem statement?

2023-03-28 Thread Jen Linkova
and money) into developing new solutions for the legacy protocol version. Especially as we expect IPv4 to decline over time. Am I missing some key benefits of the proposed solution which would make IPREF attractive enough to deploy instead of existing solutions? -- SY, Jen Linkova

[Int-area] Re: ICMP multi-part extension for XLAT IPv6 source [New I-D: equinox-intarea-icmpext-xlat-source-00]

2024-07-05 Thread Jen Linkova
on of an ICMP Multi-part Extension >>to carry the original IPv6 source address of ICMPv6 messages >>translated to ICMP by stateless (RFC6145) or stateful (RFC 6146) >>protocol translators. >> >> ___ >> Int-area mailing list >> Int-area@ietf.org >> https://www.ietf.org/mailman/listinfo/int-area > > ___ > Int-area mailing list > Int-area@ietf.org > https://www.ietf.org/mailman/listinfo/int-area -- Cheers, Jen Linkova ___ Int-area mailing list -- int-area@ietf.org To unsubscribe send an email to int-area-le...@ietf.org

[Int-area] Fwd: New Version Notification for draft-equinox-intarea-icmpext-xlat-source-01.txt

2024-07-07 Thread Jen Linkova
rom: Date: Mon, Jul 8, 2024 at 5:28 AM Subject: New Version Notification for draft-equinox-intarea-icmpext-xlat-source-01.txt To: David 'equinox' Lamparter , Jen Linkova A new version of Internet-Draft draft-equinox-intarea-icmpext-xlat-source-01.txt has been successfully submitted by Je

[Int-area] Re: ICMP multi-part extension for XLAT IPv6 source [New I-D: equinox-intarea-icmpext-xlat-source-00]

2024-07-07 Thread Jen Linkova
-00.html >> HTMLized: >> https://datatracker.ietf.org/doc/html/draft-equinox-intarea-icmpext-xlat-source >> >> >> Abstract: >> >>This document suggests the creation of an ICMP Multi-part Extension >>to carry the original IPv6 source address of ICMPv6 messages >&g

[Int-area] Re: Call for Adoption: draft-fenner-intarea-extended-icmp-hostid-02 (End 09/20/2024)

2024-09-05 Thread Jen Linkova
__________ > Int-area mailing list -- int-area@ietf.org > To unsubscribe send an email to int-area-le...@ietf.org -- Cheers, Jen Linkova ___ Int-area mailing list -- int-area@ietf.org To unsubscribe send an email to int-area-le...@ietf.org

[Int-area] A very late comment on draft-ietf-intarea-extended-icmp-nodeid-02

2025-07-23 Thread Jen Linkova
of IP/ICMP translators [RFC7915]." IMHO it would be desirable to rephrase "defaults to off" using normative language. Thanks! -- Cheers, Jen Linkova ___ Int-area mailing list -- int-area@ietf.org To unsubscribe send an email to int-area-le...@ietf.org

[Int-area] Re: draft-ietf-intarea-icmp-exten-hdr-len-03 ietf last call Opsdir review

2025-07-29 Thread Jen Linkova
torial comments. > > Ron > > > Juniper Business Use Only > > ________ > From: Jen Linkova via Datatracker > Sent: Tuesday, July 29, 2025 6:02 AM > To: ops-...@ietf.org > Cc: draft-ietf-intarea-icmp-exten-hdr-len@ietf.org > ; int-area@ietf

[Int-area] draft-ietf-intarea-icmp-exten-hdr-len-03 ietf last call Opsdir review

2025-07-29 Thread Jen Linkova via Datatracker
Document: draft-ietf-intarea-icmp-exten-hdr-len Title: ICMP Extension Header Length Field Reviewer: Jen Linkova Review result: Has Nits The document is short and straitforward. I do have one general question - more for the resposible AD, probably, and a few editorial comments - please treat them