I think that SLAAC should be deployed in the sites which use the prefixes
longer than 64. 

Don't put a limit on the prefix length.

DHCPv6 can be deployed in the sites which use the prefixes longer than
64.Why can't SLAAC?

It is not reasonable.

 

No. EUI-64 requires 64 bit host id's.  48 bits is from the MAC.  How would
you plan to squeeze blood out of the proverbial turnip?

 

 

010100110110010101101101011100000110010101110010001000000100011001101001

Jeremy Duncan

Defense Threat Reduction Agency (DTRA)
BE-BI INFOCON 3, IPv6 Architect
Command Information
Google Voice:  (540) 440-1193

  _____  

From: [email protected] [mailto:[email protected]] On Behalf Of Yu
Hua bing
Sent: Thursday, March 03, 2011 9:50 AM
To: [email protected]; Brian E Carpenter
Cc: Thomas Narten; ipv6; Scott W Brim
Subject: [BULK] Re: draft-yhb-6man-slaac-improvement-00
Importance: Low

 

I think that SLAAC should be deployed in the sites which use the prefixes
longer than 64. 

Don't put a limit on the prefix length.

DHCPv6 can be deployed in the sites which use the prefixes longer than
64.Why can't SLAAC?

It is not reasonable.

 

From: TJ <mailto:[email protected]>  

Sent: Thursday, March 03, 2011 6:58 AM

To: Brian <mailto:[email protected]>  E Carpenter 

Cc: Scott W Brim <mailto:[email protected]>  ; Thomas Narten
<mailto:[email protected]>  ; ipv6 <mailto:[email protected]>  ; huabing yu
<mailto:[email protected]>  

Subject: Re: draft-yhb-6man-slaac-improvement-00

 

On Wed, Mar 2, 2011 at 17:32, Brian E Carpenter
<[email protected]> wrote:

 

<snip>

 

I'd rather get IPv6 deployed in a uniform way first.

 

I'd take that sentence a step or two further:

"I'd rather get IPv6 deployed in a uniform way." 

or even simpler: 

"I'd rather get IPv6 deployed."

 

 

To be (perhaps overly) blunt: IMHO the changes proposed in this draft create
unneeded confusion, solve a problem that is either non-existent or is
readily solved in other ways and can create functional problems / detriments
to actual deployment.   

 

Note: I am ready, willing and (often!) able to be proven wrong ... (and
welcome the conversation!) 

 

 

 

/TJ

Attachment: smime.p7s
Description: S/MIME cryptographic signature

--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to