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/[email protected]/
[ipv6-wg] Last Call (20101123) on changes: Requirements For IPv6 in ICT Equipment
- Previous message (by thread): [ipv6-wg] Last Call (20101123) on changes: Requirements For IPv6 in ICT Equipment
- Next message (by thread): [ipv6-wg] Last Call (20101123) on changes: Requirements For IPv6 in ICT Equipment
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marco Hogewoning
marcoh at marcoh.net
Sat Nov 20 17:28:25 CET 2010
On 20 nov 2010, at 12:32, Jan Zorz @ go6.si wrote: > On 19.11.2010 14:59, Ivan Pepelnjak wrote: >> Editorial comment: the bullet ... >> >> "If 6PE is requested, the equipment must comply with "Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE)” [RFC4798]" >> >> ... in the "router or layer-3 switch" section is rephrased somewhat more generically in the bullet ... >> >> "If MPLS functionality (for example, BGP-free core, MPLS TE, MPLS FRR) is requested, the PE-routers and route reflectors must support "Connecting IPv6 Islands over IPv4 MPLS Using IPv6 Provider Edge Routers (6PE)" [RFC 4798]" >> >> ... in the same section. I would suggest we remove the first one. >> >> Ivan Pepelnjak >> www.ioshints.info/about > > Pipi hi, thnx for comment. > > Chairs, can we include this as a minor editorial change in final document, if there are no other comments? > > I suggest we publish this document as v.1 and then start accumulating proposed ideas for v.2. [Puts on his chair hat, as David is on vacation] Thanks for commenting. Looking at the tekst you are right that there is some redundancy in the text, but it's not a conflict and it does not create ambiguity. The underlying message stays the same "If you need MPLS, you need RFC 4798". Procedural I would like to publish as is instead of going into another cycle of editing and last call. No doubt in this next cycle there will be something else and the story will continue forever. At the meeting last week I spoke to various people who really want this to become official and get the draft label removed from it, so they can refer to it in their procedures. If there is anybody who has objections to publish the text as it's currently is, please state this clearly. I suggest we collect the editorial comments and fix them in a future version. Ivan, are you ok with this ? MarcoH IPv6 WG co-chair
- Previous message (by thread): [ipv6-wg] Last Call (20101123) on changes: Requirements For IPv6 in ICT Equipment
- Next message (by thread): [ipv6-wg] Last Call (20101123) on changes: Requirements For IPv6 in ICT Equipment
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]