IETF Logo Mail Archive

Re: [MEXT] Comments on draft-ietf-mext-binding-revocation-02

"Ahmad Muhanna" <amuhanna@nortel.com> Tue, 06 January 2009 15:37 UTC

Return-Path: <mext-bounces@ietf.org>
X-Original-To: mip6-archive@megatron.ietf.org
Delivered-To: ietfarch-mip6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 138D33A687D; Tue, 6 Jan 2009 07:37:57 -0800 (PST)
X-Original-To: mext@core3.amsl.com
Delivered-To: mext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 477D63A687D for <mext@core3.amsl.com>; Tue, 6 Jan 2009 07:37:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.318
X-Spam-Level:
X-Spam-Status: No, score=-6.318 tagged_above=-999 required=5 tests=[AWL=0.281, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dAa9yAF0Bt8q for <mext@core3.amsl.com>; Tue, 6 Jan 2009 07:37:54 -0800 (PST)
Received: from zrtps0kn.nortel.com (zrtps0kn.nortel.com [47.140.192.55]) by core3.amsl.com (Postfix) with ESMTP id 4863A3A6807 for <mext@ietf.org>; Tue, 6 Jan 2009 07:37:54 -0800 (PST)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com [47.103.123.71]) by zrtps0kn.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n06FbSg25804; Tue, 6 Jan 2009 15:37:29 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 06 Jan 2009 09:36:46 -0600
Message-ID: <C5A96676FCD00745B64AE42D5FCC9B6E1C73080F@zrc2hxm0.corp.nortel.com>
In-Reply-To: <C5A96676FCD00745B64AE42D5FCC9B6E1C7307B3@zrc2hxm0.corp.nortel.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [MEXT] Comments on draft-ietf-mext-binding-revocation-02
Thread-Index: AclbLn3taqHuU6TUSgeN3dxQhl2ykQArrD7gALKdDZAEWRBysAACEXzA
References: <A39C75E50DED4C43A4B0EA9B51B0B6B340478F@EUEX02.eu.qualcomm.com><C5A96676FCD00745B64AE42D5FCC9B6E1C2CF213@zrc2hxm0.corp.nortel.com><A39C75E50DED4C43A4B0EA9B51B0B6B3404AC6@EUEX02.eu.qualcomm.com> <C5A96676FCD00745B64AE42D5FCC9B6E1C7307B3@zrc2hxm0.corp.nortel.com>
From: Ahmad Muhanna <amuhanna@nortel.com>
To: "Stupar, Patrick" <pstupar@qualcomm.com>
Cc: mext@ietf.org
Subject: Re: [MEXT] Comments on draft-ietf-mext-binding-revocation-02
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: mext-bounces@ietf.org
Errors-To: mext-bounces@ietf.org

Minor typo correction.

Regards,
Ahmad

> 
> [Ahmad]
> I believe that "MUST" is needed because revoking the IPv4 HoA 
> address only does not mean deleting the BCE, In other words, 
> the MAG should maintain the IPv6 HoA Binding and a PBA is 
> needed to confirm to the LMA that the MAG will continue 
> maintaining the IPv6 binding. However, the case you mentioned 
> is an error scenario and we may have two ways to do
> it:
> 
> 1. The MAG to ignore the BRI
> 2. The MAG MUST treat this as if the 'A' bit is set and MUST 
> send a PBA.
> 

[Ahmad]
Couple of instances refer to PBA, I meant to say BRA.

> After introducing the "IPv4 HoA Revocation Only" flag, I 
> believe the proper behavior is No. 2 above.
> 
>  
_______________________________________________
MEXT mailing list
MEXT@ietf.org
https://www.ietf.org/mailman/listinfo/mext

v2.23.0 | Report a Bug | By Email