[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[sig-policy]RE: [sig-ipv6]Let's restart discussion about RIPE-261
Sorry for late response.
Yesterday, i got a local meeting outside of my office.
However, thank you for your information.
Let's discuss deeply....
Yong Wan Ju
=============================================================
IP Address Management Team in Korea Network Information Center
Manager Yong Wan Ju / Tel : +82-2-2186-4536 Mail : ywju@nic.or.kr
=============================================================
> -----Original Message-----
> From: Michel Py [mailto:michel@arneill-py.sacramento.ca.us]
> Sent: Thursday, May 29, 2003 12:05 AM
> To: YongWan Ju; sig-policy@apnic.net; sig-ipv6@apnic.net
> Subject: RE: [sig-ipv6]Let's restart discussion about RIPE-261
>
>
> Yong Wan Ju,
>
>
> > Yong Wan Ju wrote:
> > As you may know, I remember we discussed "IPv6-sparse
> > allocation" (Refer to
> > http://www.ripe.net/ripe/docs/ipv6-sparse.html) in
> > previous APNIC OPM but we didn't come to any conclusion.
>
> It might be of interest to you and the APNIC community to know that
> something very close to this mechanism has been published by the IETF as
> RFC3531 (http://www.ietf.org/rfc/rfc3531.txt). During the process and
> discussing this with many people I have never heard that it was not a
> good idea.
>
> FWIW, I would recommend proceeding with this.
>
> However, the choice of the block to be used is critical. In the
> discussion about the issues Gert Doering raised (I will send another
> email to the list) I did rate the CAP system proposed in RIPE-261 as my
> last choice because the CAP prefix (2000::/3) was too big and did not
> leave any room to special or unforeseen purposes.
>
>
> Best,
> Michel.
>
>
> _ ____ __ __ ____ _ _ _ _
> | | | _ \ \ \ / / / ___| | \ / | | | | |
> Michel Py | | | |_| | \ \ / / | |__ | \/ | | |__| |
> Sr. Network Engineer | | | __/ \ \/ / | _ \ | \ / | | __ |
> CCIE #6673 | | | | \ / | |_| | | |\/| | | | | |
> mpy@ieee.org |_| |_| \/ \___/ |_| |_| |_| |_|
> IPv6 Multihoming Solutions
> http://arneill-py.sacramento.ca.us/ipv6mh
> http://arneill-py.sacramento.ca.us/public/ipv6mh/
