Re: [MEXT] [netlmm] FW: comment ondraft-ietf-mext-binding-revocation-01
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MEXT] [netlmm] FW: comment ondraft-ietf-mext-binding-revocation-01



Hello Domagoj

Please see inline.

----- Original Message ----- 
From: "Premec, Domagoj" <domagoj.premec at siemens.com>
To: "Vijay Devarapalli" <vijay at wichorus.com>; "Ahmad
Muhanna" <amuhanna at nortel.com>
Cc: "Netlmm" <netlmm at ietf.org>; <mext at ietf.org>
Sent: Tuesday, October 14, 2008 4:49 PM
Subject: Re: [MEXT] [netlmm] FW: comment
ondraft-ietf-mext-binding-revocation-01

> Vijay,
>
>> First of all, RFC 5213 did not extend the binding cache
>> entry
>> structure to store both the control plane and data plane
>> addresses. RFC 5213 does not specify that the LMA should
>> store both the source address of the PBU and the address
>> in
>> the altCoA option in the binding cache.
>
> This is not a problem from the perspective of RFC 5213 as
> the LMA does not send unsolicited messages to the MAG. In
> the context of RFC 5213 there is no need to store both the
> alt-CoA and the source IP of the PBU in the BCE, so I
> wouldn't expect RFC 5213 to specify any extensions to the
> BCE in this regard.
>
[Yungui] The LMA may send the unsolicited messages to the
MAG, such as heartbeat request message introduced in
draft-ietf-netlmm-pmipv6-heartbeat-00.txt.
However, I agree with Vijay's opinion in the last mail,
"...In other words, the binding revocation document should
not care about the use of AltCoA option."
It's okey to make the binding revocation document comply 
with
RFC3775 and RFC5213.

In fact, in RFC3775, section 9.5.4. Sending Binding
Acknowledgements, is described:
" ...If the Source Address field of the IPv6 header that
carried the Binding Update does not contain a unicast
address, the Binding Acknowledgement MUST NOT be sent and
the Binding Update packet MUST be silently discarded.
Otherwise, the acknowledgement MUST be sent to the Source
Address."
In RFC5213, there are some similiar description for PBA
(section 5.3.6).
Therefore, it seems the source address should be saved in
the BCE.

B.R.
Yungui



_______________________________________________
MEXT mailing list
MEXT at ietf.org
https://www.ietf.org/mailman/listinfo/mext



Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.