[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Protocol Action: 'Deprecation of "ip6.int"' to BCP
- To: v6ops@ops.ietf.org
- Subject: Re: Protocol Action: 'Deprecation of "ip6.int"' to BCP
- From: Tim Chown <tjc@ecs.soton.ac.uk>
- Date: Thu, 25 Aug 2005 11:51:16 +0100
- In-reply-to: <E1E7yLj-0000O4-Bl@newodin.ietf.org>
- Mail-followup-to: v6ops@ops.ietf.org
- References: <E1E7yLj-0000O4-Bl@newodin.ietf.org>
- User-agent: Mutt/1.4i
I think this document release is very welcome.
But has anyone a detailed list of usage of .int, i.e. what practical steps
need to be taken/encouraged wrt OSes, vendors, etc to get the BCP to reality?
Tim
On Wed, Aug 24, 2005 at 12:43:39PM -0400, The IESG wrote:
> The IESG has approved the following document:
>
> - 'Deprecation of "ip6.int" '
> <draft-huston-ip6-int-03.txt> as a BCP
>
> This document has been reviewed in the IETF but is not the product of an
> IETF Working Group.
>
> The IESG contact person is Bert Wijnen.
>
> A URL of this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-huston-ip6-int-03.txt
>
> Technical Summary
>
> This document advises of the deprecation of the use of "ip6.int" for
> Standards Conformant IPv6 implementations.
>
> Working Group Summary
>
> This is not a Working Group Document.
> This memo has been prepared as part of the activities of an ad hoc
> advisory committee to advise the IAB on a number of matters relating
> to IPv6.
>
> Protocol Quality
>
> The document has been reviewed by both OPS Area ADs.
> The IETF Last Call has been specifically pointed out to the
> DNSOP and IPv6 Working Groups to ensure their attention and
> review. Further the IETF Last Call has also been pointed out
> to the RIRs for their attention and review.
>
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf-announce
--
Tim/::1