[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 ]
Jan Zorz @ go6.si
jan at go6.si
Fri Oct 21 22:52:45 CEST 2011
On 10/21/11 10:32 AM, Ivan Pepelnjak wrote: > Also keep in mind that RIPE-501(bis) addresses a very specific need: > helping IT managers select the best real-life IPv6-capable > equipment. Hi, Indeed. That's the intention :) > > We could put together the best list of RFCs and drafts, but if nobody > supports them (and thus an IT manager using RIPE-501bis cannot buy > the boxes he needs), we've just shot ourselves in the foot ... unless > you word the document in a way that says RFC-xxxx is mandatory, but > RFC-yyyy is highly recommended as its replacement and brings you > bonus points. I think it is that way (as we already had this discussion in the past)... Well established RFC is mandatory, "upgrade" optional - so I like to think :) /jan
- 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 ]