[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Posted a new copy of CPE Rtr draft
-----Original Message-----
From: Iljitsch van Beijnum [mailto:iljitsch@muada.com]
Sent: Wednesday, August 19, 2009 5:55 AM
To: Hemant Singh (shemant)
Cc: Wes Beebee (wbeebee); v6ops@ops.ietf.org
Subject: Re: Posted a new copy of CPE Rtr draft
>Hm, looks like you're keeping the text the same in the majority of the
>cases. As you may expect, that doesn't make me particularly happy.
Sorry, we forgot to edit the -01 for two places I said we'd make a
change. The one place was to remove the "preferred to be Ethernet" and
other places was to make a sentence better in the ND Proxy section as
follows:
[If a CPE Router will never be deployed in an environment with these
characteristics, then ND Proxy is not necessary.].
All other agreement for changing any MAY to a MUST was only agreed by us
but I said the broader mailer has to agree to such a change and that is
why we didn't make any such MAY to MUST changes.
>Also, pointing to general discussions a while ago is not a very
>satisfactory response, this would require me to sift through the
>archives in the hopes of finding the argument you have in mind, a
>procedure that is time consuming and error prone.
There were two cases in my response that pointed to the v6ops archives.
I'd be happy to explain the two cases here.
Case (a) the ULA discussion. Here is the reasoning. Brian Carpenter
gave the dentist example and we all agreed to keep ULA permanent (if at
all the CPE Rtr decides to support ULA) because if the SP network goes
down, the GUA in the home is no longer active. In such a case, the ULA
is still active and folks in the home can print to their printer or what
have you.
Case (b) strong host model sentence and Shin M.'s request. NTT (I
believe it is NTT West) in Japan has hacked up routing code they provide
to their broadband customers to run the code on a Windows PC. So this
happens to be a router running under Windows. Now once can see how do
strong vs. weak host models get into play.
Hemant