Re: [v6ops] draft-xli-v6ops-ivi-icmp-address (was re: Fwd: 82nd IETF DRAFT Agenda)

["George, Wes" <[e-mail]>]

I share some of the concerns raised by other folks regarding how this gets treated across AS boundaries, but probably this means that it's useful discussion to have in a WG meeting to determine if there is a way to meet the needs of the solution without creating concerns for operators about the traffic.

However, I'd like to pose a different question -
This is basically an effort to complete previously incomplete work on RFC6145, which was managed through BEHAVE. I know that BEHAVE is likely being closed down, but based on my read of the AD and list discussion, this was because there was not enough additional work to be undertaken to justify a recharter. No commentary intended on that front, but should we expect that our WG, which was already trying to find work to shed will now be seeing more orphaned BEHAVE work? Should we perhaps be pushing back on the decision to close down BEHAVE, or pushing back on those who are pursuing additional work in that space given that the consensus seems to be "we're done now"?

Thanks
Wes George


> >> I'm looking for (and in some cases have seen) commentary on each of:
> >>
> >> -rw-rw-r--  1 fred  fred  13796 Jul 25 23:59
> >> draft-xli-v6ops-ivi-icmp-address-00.txt
> >
> > I would like to request that the V6ops WG adopt draft-xli-v6ops-ivi-
> icmp-address-00.txt as a WG adoption.
> >
> > The draft describes the operational considerations of mapping ICMPv6
> packets through an RFC6145 gateway where the IPv6 address is not
> directly translatable into an IPv4 address, and requests an IANA
> Special Purpose IPv4 address allocation (192.70.192.0/24) to allow this
> address mapping to take place using a protocol-specific designated
> address block in IPv4.
> >
> > The authors are hopeful that this will not require any valuable face-
> to-face WG time at IETF 82 and the WG's consideration of this document
> can be undertaken entirely on the mailing list.
> >
> > Regards,
> >
> > xing
> >

This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.