IETF Logo Mail Archive

Re: [dhcwg] Updating RFC 3633 with draft-ietf-dhc-dhcpv6-prefix-length-hint-issue

Erik Kline <ek@google.com> Tue, 21 February 2017 05:57 UTC

Return-Path: <ek@google.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A2CD129AE7 for <dhcwg@ietfa.amsl.com>; Mon, 20 Feb 2017 21:57:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 mNTaMQ57_W2l for <dhcwg@ietfa.amsl.com>; Mon, 20 Feb 2017 21:57:39 -0800 (PST)
Received: from mail-yw0-x234.google.com (mail-yw0-x234.google.com [IPv6:2607:f8b0:4002:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63464129AE4 for <dhcwg@ietf.org>; Mon, 20 Feb 2017 21:57:39 -0800 (PST)
Received: by mail-yw0-x234.google.com with SMTP id l19so59495867ywc.2 for <dhcwg@ietf.org>; Mon, 20 Feb 2017 21:57:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=YHKz7FwC7K+E2twPpKlShOEvsrZJ09wSz7jUKvkwIfI=; b=oSH+4rt/tfCJBd6wxISrdyyhI8t9Dker9/RIcDxqFV8/sRH3nc7uxzZYw9MH1dOt/U w6tn0MoeJ+rhySqTcMgFW+WrkC9Zdtb3t8r4iBXpJ0dsmZsUaUzCiNLmy7cy78ztMe5z 4qrwIg2Jh4PoSBcNAufBIf9F0Cl4+aAKSFPeLeaUbD5jmNn2DYx6mG4whJEdgSSz/PnT VVx3ZGdh4rcQQy4H0ZlxAsR/2cMMLcgXvZl0O22LfGy/F/7w8/O240GqCeQ+Q39myyp+ Qb44VXLYOS3LEOXVNdJ4GirK+DzSOk9gWFfdAj/C6P3kwq24zE258A9Hf0czzNAPLXlO fPew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=YHKz7FwC7K+E2twPpKlShOEvsrZJ09wSz7jUKvkwIfI=; b=HrIo0ZhusITGNb2mcyt0tryBQss4lWwncxI29rHnFsqelBvnM1eNtCEafXr3uoARNT OSq7g95cpXJLSMQzqq5lSLTnNuDSi0apxAhO2vmR7L3UOsV9dY8829HvkKX32e0PTCBv KbRaYIlsBDB4lWK2A6HA/6QiNUGYsxVRpRzKaW8QuH2QYhrlOoQcgIJyaCtYSbsfuuxE IFBOvyuinGjayw1w6Gg1SGUvMS1e9CXo2hrHCPKr1JvQn3v+09K/blFkrlsXPP+eVRcH Jz+QjOtRuYLOzzsw+h2d5Vud0OePtJ+hb1RwtWbtbb+nX3bEt+vaRLMf+/E9ZD0JAo2P oOSw==
X-Gm-Message-State: AMke39mhBVs3xTIWkzhUbEnCF65B7UBYrxkmBJ3YMhzMe5m+fn+wKvI9r/BPCFsbfR26exY5yp76ZGlcVTX0TNpu
X-Received: by 10.129.41.69 with SMTP id p66mr15583139ywp.223.1487656658154; Mon, 20 Feb 2017 21:57:38 -0800 (PST)
MIME-Version: 1.0
Received: by 10.37.207.4 with HTTP; Mon, 20 Feb 2017 21:57:17 -0800 (PST)
In-Reply-To: <DE41B94D-78C3-4BDE-8BA3-555D67A59E49@ericsson.com>
References: <CAFx+hEMNhzShhDWxSX+JLq+KPk4HyMzdGMEWYWG6i1o+LFMb3w@mail.gmail.com> <DE41B94D-78C3-4BDE-8BA3-555D67A59E49@ericsson.com>
From: Erik Kline <ek@google.com>
Date: Tue, 21 Feb 2017 14:57:17 +0900
Message-ID: <CAAedzxp_OtzTg+H8XqLS0x-ry7VVknwduD87AheAP4_cvpjwqA@mail.gmail.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="001a114160bab1b7ca0549040e6e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/sMFEiMB7dnCT7N3gg_zcLJp7MmY>
Cc: dhcwg <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>
Subject: Re: [dhcwg] Updating RFC 3633 with draft-ietf-dhc-dhcpv6-prefix-length-hint-issue
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 21 Feb 2017 05:57:41 -0000

What about folding in to 3315bis (where other 3633 info is going)?  I have
no strong preference one way or the other, just asking.

On 21 February 2017 at 13:06, Suresh Krishnan <suresh.krishnan@ericsson.com>
wrote:

>
> > On Feb 17, 2017, at 12:32 AM, tianxiang li <peter416733@gmail.com>
> wrote:
> >
> > Hi all,
> >
> > The IESG review of draft-ietf-dhc-dhcpv6-prefix-length-hint-issue has
> ended, several reviewers suggested this document should update RFC 3633, as
> someone reading RFC3633 would need a pointer to this document. Hope to
> receive the comments from the WG regarding this issue.
>
> I personally have no objections to adding the Updates: RFC3633 tag to the
> document. It would be great if other WG participants can chime in one way
> or another.
>
> >
> > And if so, do we need to add a specific tag in the xml file stating that
> it updates RFC 3633 and change the title of the document?
>
> If the WG has no objection to doing this, I can add this (Updates tag) as
> an RFC Editor note. No need for a new rev.
>
> Thanks
> Suresh
>
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
>
>

v2.23.0 | Report a Bug | By Email