Fred,
I'm not going to discuss this text with you any further on the list at this
time. I believe the text is sufficiently unclear and imprecise to result in
confusion about how one should implement the MN-AR interface in NETLMM.
Clearly, you disagree and you're not prepared to accommodate any of my
suggestions, so there's little point in our continuing the discussion.
jak
----- Original Message -----
From: "Templin, Fred L" <[EMAIL PROTECTED]>
To: "James Kempf" <[EMAIL PROTECTED]>; "INT Area"
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; "IETF IPv6 Mailing List"
<ipv6@ietf.org>
Sent: Thursday, August 24, 2006 1:14 PM
Subject: RE: [Int-area] RE: [netlmm] Multilink Subnet Considerations for
NETLMMAddressing
jak>> What are your expectations about what advertising 'L=1' means
for the
link?
The criteria that allow a prefix to be advertised with 'L=1' are
covered under the final paragraph of the offered text, and what
advertising 'L=1' means for the link is covered under RFC2461.
The point of the offered text is that by following the guidelines
a NETLMM domain cannot be a multilink subnet. I can call it something
like "Multilink Subnet Avoidance" if you'd like.
jak>> "Cannot avoid a multilink subnet"? Then why call it "Multilink
Subnet
Avoidance"?'
I don't quite understand your question, but the offered text avoids
multilink subnets.
Fred
[EMAIL PROTECTED]
jak
Here is the offered text again:
"5. Multilink Subnet Considerations
An individual prefix is an IP prefix associated with a specific
MN, and a shared prefix is an IP prefix that may be associated
with multiple MNs.
ARs must not include an individual prefix in RAs that may be
received by a MN other than the one associated with the prefix.
ARs must not send RAs that include a shared prefix in a Prefix
Information Option with 'A'=1 unless there is operational assurance
of duplicate address detection/avoidance across the NETLMM domain.
ARs must not send RAs that include an individual or shared prefix
in a Prefix Information Option with 'L'=1 unless all RAs that
include the prefix and all MNs that receive them are associated
with a single link."
Fred
[EMAIL PROTECTED]
_______________________________________________
Int-area mailing list
Int-area@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/int-area
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
