This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ipv6-wg@ripe.net/
[ipv6-wg] Last call on the replacement of ripe-501 "Requirements for IPv6 in ICT equipment"
- Previous message (by thread): [ipv6-wg] Last call on the replacement of ripe-501 "Requirements for IPv6 in ICT equipment"
- Next message (by thread): [ipv6-wg] Last call on the replacement of ripe-501 "Requirements for IPv6 in ICT equipment"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tassos Chatzithomaoglou
achatz at forthnetgroup.gr
Thu Oct 20 20:22:14 CEST 2011
Hi all, I noticed [I-D.ymbk-aplusp] on the list, which recently became RFC 6346. Besides updating the list, do you find it appropriate to include RFCs with experimental status? Also 3484bis is still in draft. If we include drafts, then 6204 should also be changed to 6204bis. Although i would prefer to have the final RFCs in. -- Tassos Marco Hogewoning wrote on 13/10/2011 12:15: > Dear colleagues, > > Following up on feedback received from the community during and after the publication of the ripe-501. The authors have worked on a replacement document, incorporating suggestions made by the community and clarifying some of the requirements. Prior draft versions of this document have been posted to this mailing list in the past months. > > The resulting final draft document is now published on the website and reachable via https://www.ripe.net/ripe/docs/other-documents/requirements-for-ipv6-in-ict-equipment > > We would like the community to review this document. Although this is not a formal policy proposal, we would like to issue a 4 week working group last call on this draft before publication. > > Minor changes like typos or formatting can be sent to the authors or to me directly. Please raise any questions or comments on the content to this list. Unless blocking issues are found on this text, it is our intent to publish this draft as a RIPE Document and to change the status of the current document ripe-501 to obsolete, with a reference to the new document. > > The authors will also present on this draft during the IPv6 working group session at the Vienna meeting. > > Please send any comments before Thursday November 10 2011, which is 4 weeks from now. > > Regards, > > Marco Hogewoning > on behalf of the IPv6 Working Group chairs > >
- Previous message (by thread): [ipv6-wg] Last call on the replacement of ripe-501 "Requirements for IPv6 in ICT equipment"
- Next message (by thread): [ipv6-wg] Last call on the replacement of ripe-501 "Requirements for IPv6 in ICT equipment"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]