On 11/26/2011 4:36 PM, Suresh Krishnan wrote:
Hi Adrian,
On 11/25/2011 05:03 PM, Adrian Farrel wrote:
Hi,
This thread seems to have dried up. AFAICS there is no change needed to the
document.
Anything further to say before I ask Russ to clear his Discuss?
I had a chat about this draft with Stig at the IETF meeting in Taipei.
He clarified how PIM PORT connections can be shared across address
families.
I believe the following text change would resolve my concern with the draft.
OLD:
If two neighbors announce the same transport (TCP or SCTP) and the same
Connection IDs in the IPv4 and IPv6 Hello messages, then only one
connection is established and is shared. Otherwise, two connections
are established and are used separately.
I guess something needs to be added. I think it is said implicitly here
since we are stating "the same ConnectionIDs in the IPv4 and IPv6"...,
also there would not be much use for the AFI in the hello option if it
was always the same as the hello itself. Anyway, I agree it should be
pointed out.
NEW:
If two neighbors announce the same transport (TCP or SCTP) and the same
Connection IDs in the IPv4 and IPv6 Hello messages, then only one
connection is established and is shared. Otherwise, two connections
are established and are used separately.
Please note that the Connection ID AFI in the PORT Hello Option does not
need to match the address family of PIM Hello message that carries it.
e.g. an IPv6 PIM Hello message could contain a PORT Hello Option with a
TCP Connection ID AFI of 1 (IPv4).
While I am OK with this text, wouldn't it be better to add this to 3.1
and 3.2 where we formally define the hello options?
My proposal would be:
End of 3.1:
OLD:
TCP Connection ID AFI: The AFI value to describe the address-family
of the address of the TCP Connection ID field. When this field is
0, a mechanism outside the scope of this document is used to
obtain the addresses used to establish the TCP connection.
NEW:
TCP Connection ID AFI: The AFI value to describe the address-family
of the address of the TCP Connection ID field. Note that this
value does not need to match the address-family of the PIM Hello
message that carries it. When this field is 0, a mechanism
outside the scope of this document is used to obtain the
addresses used to establish the TCP connection.
End of 3.2:
OLD:
SCTP Connection ID AFI: The AFI value to describe the address-
family of the address of the SCTP Connection ID field. When this
field is 0, a mechanism outside the scope of this document is used
to obtain the addresses used to establish the SCTP connection.
NEW:
SCTP Connection ID AFI: The AFI value to describe the address-
family of the address of the SCTP Connection ID field. Note that
this value does not need to match the address-family of the PIM
Hello message that carries it. When this field is 0, a mechanism
outside the scope of this document is used to obtain the
addresses used to establish the SCTP connection.
What do you think?
Stig
Thanks
Suresh
_______________________________________________
Gen-art mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/gen-art
