Re: [dhcwg] FYI: Reminder - WGLC for draft-ietf-dhc-access-network-identifier-02 - respond by April 27, 2014

John Kaippallimalil <John.Kaippallimalil@huawei.com> Wed, 23 April 2014 23:12 UTC

Return-Path: <John.Kaippallimalil@huawei.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 199171A072A for <dhcwg@ietfa.amsl.com>; Wed, 23 Apr 2014 16:12:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.473
X-Spam-Level:
X-Spam-Status: No, score=-4.473 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pDP8wQi5kVop for <dhcwg@ietfa.amsl.com>; Wed, 23 Apr 2014 16:12:22 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 275EA1A0299 for <dhcwg@ietf.org>; Wed, 23 Apr 2014 16:12:22 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BGA08654; Wed, 23 Apr 2014 23:12:15 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 24 Apr 2014 00:11:33 +0100
Received: from DFWEML704-CHM.china.huawei.com (10.193.5.141) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 24 Apr 2014 00:12:14 +0100
Received: from DFWEML703-CHM.china.huawei.com ([169.254.5.104]) by dfweml704-chm.china.huawei.com ([169.254.6.56]) with mapi id 14.03.0158.001; Wed, 23 Apr 2014 16:12:05 -0700
From: John Kaippallimalil <John.Kaippallimalil@huawei.com>
To: "volz@cisco.com" <volz@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: FYI: Reminder - WGLC for draft-ietf-dhc-access-network-identifier-02 - respond by April 27, 2014
Thread-Index: AQHPX0lwvXI+YnXlrEmWFnJb/SOmCg==
Date: Wed, 23 Apr 2014 23:12:04 +0000
Message-ID: <6561EABF52675C45BCDACA1B4D7AA1171D9DA006@dfweml703-chm.china.huawei.com>
References: <6561EABF52675C45BCDACA1B4D7AA1171D9D9FEF@dfweml703-chm.china.huawei.com>
In-Reply-To: <6561EABF52675C45BCDACA1B4D7AA1171D9D9FEF@dfweml703-chm.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.192.11.139]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/JV8LVGlhIQbwm6tcQaBxI8QQVbs
Cc: "mgrayson@cisco.com" <mgrayson@cisco.com>
Subject: Re: [dhcwg] FYI: Reminder - WGLC for draft-ietf-dhc-access-network-identifier-02 - respond by April 27, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Apr 2014 23:12:24 -0000

Hi,
I went through the draft and think that it is useful and well written.

A couple of comments that you may want to consider:
1. In 6.2, if we have a PLMN Identifier as Network Identifier for 3GPP RAN network. What would be the Access Technology Type in 6.1. in this case?
It may be useful to add some of the RAN types (that apply for PLMNs) to the ANI list in 6.1.

2. Is it possible to  assert that for all ANI changes, there will be a DHCP request sent by the client. If so, perhaps it would be good to mention this somewhere in the draft.

Regards,
John


> -----Original Message-----
> Resent-From: <draft-alias-bounces@tools.ietf.org>
> From: "Bernie Volz (volz)" <volz@cisco.com>
> Date: April 21, 2014 at 1:30:53 PM PDT
> Resent-To: <jouni.nospam@gmail.com>, <mgrayson@cisco.com>,
> <sgundave@cisco.com>, <shwethab@cisco.com>
> To: "draft-ietf-dhc-access-network-identifier@tools.ietf.org" <draft-ietf-dhc-
> access-network-identifier@tools.ietf.org>
> Subject: FYI: Reminder - WGLC for draft-ietf-dhc-access-network-identifier-02
> - respond by April 27, 2014
> Hi:
> 
> Not sure if there are some people you can get to review and comment on this
> draft ... would be good so it doesn't fail WGLC.
> 
> -	Bernie
> 
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
> Sent: Monday, April 21, 2014 9:28 AM
> To: dhcwg@ietf.org
> Subject: [dhcwg] Reminder - WGLC for draft-ietf-dhc-access-network-identifier-
> 02 - respond by April 27, 2014
> 
> Friendly reminder regarding this WGLC. There has been no feedback so far.
> 
> -	Bernie
> 
> From: Bernie Volz (volz)
> Sent: Saturday, April 12, 2014 10:04 AM
> To: dhcwg@ietf.org
> Subject: WGLC for draft-ietf-dhc-access-network-identifier-02 - respond by
> April 27, 2014
> 
> Folks, the authors of draft-ietf-dhc-access-network-identifier
> (http://tools.ietf.org/html/draft-ietf-dhc-access-network-identifier-02)
> feel it's ready for work group last call. Please review this draft and
> indicate whether or not you feel it is ready to be published.
> 
> At the time of this writing, there is no IPR reported against this draft.
> Please see http://www.ietf.org/mail-archive/web/dhcwg/current/msg14143.html
> for a reminder regarding IPR disclosure requirements.
> 
> Tomek and I will evaluate consensus after April 27, 2014.
> 
> Thanks,
> Bernie & Tomek