Re: Gen-ART Review of draft-ietf-dhc-vpn-option-11.txt

Kim Kinnear <kkinnear@cisco.com> Thu, 29 October 2009 21:34 UTC

Return-Path: <kkinnear@cisco.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8E9893A69A8; Thu, 29 Oct 2009 14:34:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.932
X-Spam-Level:
X-Spam-Status: No, score=-6.932 tagged_above=-999 required=5 tests=[AWL=-0.333, 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 nUCAbNqVe1ak; Thu, 29 Oct 2009 14:34:31 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 6498F3A6800; Thu, 29 Oct 2009 14:34:31 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApoEAOum6UqtJV2Z/2dsb2JhbADHaJgdhD0EgWI
X-IronPort-AV: E=Sophos;i="4.44,648,1249257600"; d="scan'208";a="65607275"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rtp-iport-2.cisco.com with ESMTP; 29 Oct 2009 21:34:47 +0000
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rcdn-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id n9TLYk7h006606; Thu, 29 Oct 2009 21:34:47 GMT
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 29 Oct 2009 17:34:46 -0400
Received: from kkinnear-wxp01.cisco.com ([161.44.65.168]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 29 Oct 2009 17:34:45 -0400
Message-Id: <4.3.2.7.2.20091029171229.034304b0@email.cisco.com>
X-Sender: kkinnear@email.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 29 Oct 2009 17:33:48 -0400
To: Spencer Dawkins <spencer@wonderhamster.org>, draft-ietf-dhc-vpn-option@tools.ietf.org
From: Kim Kinnear <kkinnear@cisco.com>
Subject: Re: Gen-ART Review of draft-ietf-dhc-vpn-option-11.txt
In-Reply-To: <B783E8313ED6443CBD0B76241AC7BB9D@china.huawei.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-OriginalArrivalTime: 29 Oct 2009 21:34:45.0952 (UTC) FILETIME=[A26D8C00:01CA58DF]
X-Mailman-Approved-At: Fri, 30 Oct 2009 09:26:21 -0700
Cc: General Area Review Team <gen-art@ietf.org>, ietf@ietf.org, kkinnear@cisco.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Oct 2009 21:34:32 -0000

Spencer,

Thank you for your review.  My comments
are preceded by Kim:, below.

At 06:55 PM 10/21/2009, Spencer Dawkins wrote:
>I have been selected as the General Area Review Team (Gen-ART)reviewer for
>this draft (for background on Gen-ART, please
>seehttp://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).
>
>Please resolve these comments along with any other Last Call comments you
>may receive.
>
>Document: draft-ietf-dhc-vpn-option-11.txt
>Reviewer: Spencer Dawkins
>Review Date: 2009-10-21
>IETF LC End Date: 2009-10-16 (sorry!)
>IESG Telechat date: 2009-10-22 (double-sorry!)
>
>Summary: This draft is almost ready for publication as a Proposed Standard. I had two questions about 2119 language in section 5, as follows:
>
>5.  Relay Agent Behavior
>
>  A DHCPv4 relay agent SHOULD include a DHCPv4 VSS sub-option in a
>  relay-agent-information option [RFC3046], while a DHCPv6 relay agent
>  SHOULD include a DHCPv6 VSS option in the Relay-forward message.
>
>Spencer (minor): is this functionality supposed to work if either SHOULD is violated? I'm wondering why these are not MUSTs.

        Kim: No, the functionality described in this
        document will not work if either SHOULD is violated,
        though their may be some other way for the relay
        agent to get its needs met.  I guess that should
        be a MUST for this document, then.  I'll fix it.


>  The value placed in the Virtual Subnet Selection sub-option or option
>  SHOULD be sufficient for the relay agent to properly route any DHCP
>
>Spencer (minor): I don't think this is a 2119 SHOULD. I'm thinking "more like a statement of fact" - perhaps "will be sufficient"? If it's really 2119, why isn't it a MUST?

        Kim: The thinking here is that the relay agent
        can send everything it needs to route in the VSS option/sub-option.     
        But this was a SHOULD since it might have internal
        tables that remember state and so this might be
        a key into internal state that would allow it to
        work.  I'll clarify and fix this.

        Regards - Kim


>  reply packet returned from the DHCP server to the DHCP client for
>  which it is destined.
>