Subject: [MEXT] A new extension to Binding Revocation//Re : Protocol Action: 'Binding Revocation for IPv6 Mobility' to Proposed Standard

From: cuixiangsong 00111037 <[email-masked]>
Date: Sun, 08 Nov 2009 21:08:13 +0800

Hi all,

In my understanding, this Proposed Standard doesn't include
the case that CN revoks the binding from the mobile node in 
route optimization mode, and this new extension is difficult
to be included in the proposed standard, so we wrote a new
draft, please find it in the attachment.

I wish this case were included in the approved document,
but i did notice this issue just recently.

What do you think about this new extension?

Comments are always welcome!

Best Regards

Xiangsong

----- 原邮件 -----
发件人: The IESG <[email-masked]>
日期: 星期三, 十月 28日, 2009 下午11:03
主题: [MEXT] Protocol Action: 'Binding Revocation for IPv6 Mobility' to Proposed Standard
收件人: IETF-Announce <[email-masked]>
抄送: mext mailing list <[email-masked]>, Internet Architecture Board <[email-masked]>, mext chair <[email-masked]>, RFC Editor <[email-masked]>

> The IESG has approved the following document:
> 
> - 'Binding Revocation for IPv6 Mobility '
>   <draft-ietf-mext-binding-revocation-14.txt> as a Proposed Standard
> 
> 
> This document is the product of the Mobility EXTensions for IPv6 
> Working Group. 
> 
> The IESG contact persons are Jari Arkko and Ralph Droms.
> 
> A URL of this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-mext-binding-
> revocation-14.txt
> 
> Technical Summary
> 
>   This document defines a binding revocation mechanism to 
> terminate a 
>   mobile node's mobility session and the associated resources. These
>   semantics are generic enough and can be used by mobility 
> entities in
>   the case of Mobile IPv6 and its extensions. This mechanism 
> allows the
>   mobility entity which initiates the revocation procedure to request
>   its corresponding one to terminate either one, multiple or all 
>   specified binding cache entries.
> 
> Working Group Summary
> 
>   This is a product of the MEXT WG. The document's progress was 
>   coordinated with the NETLMM WG.
> 
> Document Quality
> 
>   The mechanism specified by this document is relied upon by the
>   Evolved Packet System developed by 3GPP and as thus will be
>   implemented by 3GPP vendors.
> 
> Personnel
> 
>   Document Shepherd is Julien Laganier. The Sponsoring AD
>   is Jari Arkko.
> 
> RFC Editor Note
> 
>  Add an "Updates: RFC 3775" header to the top
> 
>  Change in the Abstract:
>  OLD:
>   These
>   semantics are generic enough and can be used by mobility 
> entities in
>   the case of Mobile IPv6 and its extensions.  This mechanism allows
>   the mobility entity which initiates the revocation procedure to
>   request its corresponding one to terminate either one, multiple or
>   all specified binding cache entries.
>  NEW:
>   This mechanism can be used both with base Mobile IPv6 and
>   its extensions, such as Proxy Mobile IPv6. The mechanism allows
>   the mobility entity which initiates the revocation procedure to
>   request its peer to terminate either one, multiple or
>   all specified binding cache entries.
> 
> _______________________________________________
> MEXT mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/mext
>