[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 ]
Ivan Pepelnjak
ip at ioshints.info
Fri Oct 21 10:32:11 CEST 2011
Also keep in mind that RIPE-501(bis) addresses a very specific need: helping IT managers select the best real-life IPv6-capable equipment. 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. Just my €0.0002 Ivan > -----Original Message----- > From: ipv6-wg-bounces at ripe.net [mailto:ipv6-wg-bounces at ripe.net] On Behalf > Of Ole Troan > Sent: Friday, October 21, 2011 10:02 AM > To: Tassos Chatzithomaoglou > Cc: Marco Hogewoning; ipv6-wg at ripe.net > Subject: Re: [ipv6-wg] Last call on the replacement of ripe-501 > "Requirements for IPv6 in ICT equipment" [...] > > Also 3484bis is still in draft. > > 3484bis fixes some real problems. hopefully it will be RFC before 501 is > out.
- 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 ]