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] IPv6 on P2P links

• Previous message (by thread): [ipv6-wg] IPv6 on P2P links
• Next message (by thread): [ipv6-wg] IPv6 on P2P links

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Ivan Pepelnjak ip at ioshints.info
Thu May 26 20:19:33 CEST 2011

Nice to hear Cisco has no problems with /127 (now I don't have to test it and blog about it ;)

As for RIPE501bis - I would add RFC 6164 to the list of "optional" RFCs in the "Router requirements" section. Makes sense?

Ivan

> RIPE501Bis should imho be focused upon features for 'asking the right
> IPv6 support'... asking
> for /127 is silly I think... (btw Cisco IOS device's have no issue with
> it at all
> btw... so I am speaking here with my technology hat on).
> 
> G/

• Previous message (by thread): [ipv6-wg] IPv6 on P2P links
• Next message (by thread): [ipv6-wg] IPv6 on P2P links

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ ipv6-wg Archives ]