>>>>> On Mon, 12 Jul 2004 16:20:21 +0300, 
>>>>> "EricLKlein" <[EMAIL PROTECTED]> said:

> In reviewing this document one question comes to mind from my own personal
> experience with IPv4 network and it is related to "zero touch provisioning".
> I realize that this is for stateless provisioning, but I still could not see
> where this would fall other than here.

> Background:
> Under the standard "zero touch provisioning" situation the network
> management system (NMS) assigns an IP address to the Provider Edge (PE)
> router port. When the Customer Edge (CE) router is connected for the first
> time and then powered up it "sees" the IP address of the other end of the
> link and assigns itself the next higher one. So it looks like:

> (Provider Edge router) AAAA::0001 ---- (Customer Edge router) AAAA::0002

> Once this IP address is assigned and registering on the network the specific
> configuration required based on the services purchased are uploaded into the
> router and the new configuration and security are applied.

> Question:
> Given that this does not include a DHCP server (either v4 or v6) but
> requires explicit IP assignment from the NMS, how would this work given this
> draft?

I'm not sure if this question even has any relationship with
rfc2462bis...if it is enough for the CE to know (one of) the PE's
address in order to assign a similar address (perhaps an address with
the same prefix and a slightly different interface ID) using its own
API (like the "ifconfig" command of UNIX-like systems), then the CE
can (theoretically) use:

- inverse neighbor discovery (RFC3122), or
- ICMPv6 name lookups (draft-ietf-ipngwg-icmp-name-lookups-10.txt)

                                        JINMEI, Tatuya
                                        Communication Platform Lab.
                                        Corporate R&D Center, Toshiba Corp.
                                        [EMAIL PROTECTED]

p.s. right now, I don't think this issue (if we need to call it an
issue) is a show-stopper to advance rfc2462bis.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to