IETF Logo Mail Archive

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

tianxiang li <peter416733@gmail.com> Fri, 17 February 2017 05:32 UTC

Return-Path: <peter416733@gmail.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 1C1A11294EE for <dhcwg@ietfa.amsl.com>; Thu, 16 Feb 2017 21:32:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 wfLuYiCj3klH for <dhcwg@ietfa.amsl.com>; Thu, 16 Feb 2017 21:32:44 -0800 (PST)
Received: from mail-ot0-x232.google.com (mail-ot0-x232.google.com [IPv6:2607:f8b0:4003:c0f::232]) (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 2899612946D for <dhcwg@ietf.org>; Thu, 16 Feb 2017 21:32:44 -0800 (PST)
Received: by mail-ot0-x232.google.com with SMTP id 45so25528848otd.2 for <dhcwg@ietf.org>; Thu, 16 Feb 2017 21:32:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=UJ8sjrkEJq2fS2s3dXT4aiTMe+eyn54+3oZk0iFrQBk=; b=rPtPZILutHR+/hIKVB9tbiMfNYto/5zrBkEeiv7BYhdXcGyc0EUjz5IvmQHOcVPV+J nErWb9uc81XZS5E2+PSNntv91wsoOap0YnPMh8bIbFYKMT8fOqliPaWL2AJ9nrcyKpR0 EPv7oFj5hMyZ1v47JUXYGs3eMC0Z9XjoHBfSbzNcXWz2ASM9yiMKjOORV1hTLGXLm1fW OGFcg/J/ZJ4kLlBMsCcTSMIg2740Pg9r3ao5VR6+Hmm8SZhvEFqbNW67pGThTe9iZXQH 6aX4E2Ix8yq7L5vnOcFszsk1YlPXUhEJshYfMDiXs5/7RfX8KNLednqq6UaAaLt7uBeZ ZqQQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=UJ8sjrkEJq2fS2s3dXT4aiTMe+eyn54+3oZk0iFrQBk=; b=l2ixbpxwyulG4Etl5Qooih4T+Jc4sWPp0oG6MJC9eRWcvovZ4CCnTb16PgJ7sHAe0I LaNxzMOQZkQ2HNX9eDr4VtOXFru/2c9ZV/XZXyva178y3yyZWFrNfv+dotGKS5ReEc1C T+FMp8quxev7oZ1lOUm0hJAGxMKC1Y7FcJlZ8+34O/jL4Bj+sX3zT5+91Pf3+i4aS+tx S75TRln/R3+d+BsKIIbM0rkJxV1C62GwnzWt32eB3y8PFnstSYjI8wZ4aObD39fRkdR8 VrlG5JBGRpcUpjUSPUFr33n91LMvJaDkwItAWPTlztIpyLjaXlDnuSbQZ1ZfovfFh7zW vMDg==
X-Gm-Message-State: AMke39kLGpiMFskWrJSktGUsDiGBlAQZSlyPrXdwatUFos2uhJ/duXYX95VQDOluXE6O9r0Hb4P72LtIcyWjeg==
X-Received: by 10.157.27.169 with SMTP id z38mr3193344otd.262.1487309563591; Thu, 16 Feb 2017 21:32:43 -0800 (PST)
MIME-Version: 1.0
Received: by 10.202.1.202 with HTTP; Thu, 16 Feb 2017 21:32:03 -0800 (PST)
From: tianxiang li <peter416733@gmail.com>
Date: Fri, 17 Feb 2017 13:32:03 +0800
Message-ID: <CAFx+hEMNhzShhDWxSX+JLq+KPk4HyMzdGMEWYWG6i1o+LFMb3w@mail.gmail.com>
To: dhcwg <dhcwg@ietf.org>
Content-Type: multipart/alternative; boundary=001a113cc7fa3583250548b33e9c
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/rtb0y-GyNTcRKE3T__P8y3Nc01k>
Cc: "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: [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: Fri, 17 Feb 2017 05:32:45 -0000

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.

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?

Hope to receive your advice.

Thank you,
Tianxiang

v2.2.0 | Report a Bug | By Email