IETF Logo Mail Archive

RE: Node Requirements: Elevating DHCPv6 from MAY to SHOULD

<john.loughney@nokia.com> Fri, 13 May 2011 16:51 UTC

Return-Path: <john.loughney@nokia.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 877B3E081F for <ipv6@ietfa.amsl.com>; Fri, 13 May 2011 09:51:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.099
X-Spam-Level:
X-Spam-Status: No, score=-103.099 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gKOwhUh096pD for <ipv6@ietfa.amsl.com>; Fri, 13 May 2011 09:51:49 -0700 (PDT)
Received: from mgw-da01.nokia.com (smtp.nokia.com [147.243.128.24]) by ietfa.amsl.com (Postfix) with ESMTP id 8385AE0812 for <ipv6@ietf.org>; Fri, 13 May 2011 09:51:37 -0700 (PDT)
Received: from vaebh104.NOE.Nokia.com (vaebh104.europe.nokia.com [10.160.244.30]) by mgw-da01.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p4DGpKIk001722; Fri, 13 May 2011 19:51:36 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.7]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Fri, 13 May 2011 19:51:21 +0300
Received: from 008-AM1MMR1-003.mgdnok.nokia.com (65.54.30.58) by NOK-AM1MHUB-03.mgdnok.nokia.com (65.54.30.7) with Microsoft SMTP Server (TLS) id 8.2.255.0; Fri, 13 May 2011 18:51:20 +0200
Received: from 008-AM1MPN1-003.mgdnok.nokia.com ([169.254.3.183]) by 008-AM1MMR1-003.mgdnok.nokia.com ([65.54.30.58]) with mapi id 14.01.0289.008; Fri, 13 May 2011 18:51:20 +0200
From: john.loughney@nokia.com
To: narten@us.ibm.com
Subject: RE: Node Requirements: Elevating DHCPv6 from MAY to SHOULD
Thread-Topic: Node Requirements: Elevating DHCPv6 from MAY to SHOULD
Thread-Index: AQHMEXM/7ZYscsi4c0OIKjxfjU/lXpSK53wg///o5wCAAChyUA==
Date: Fri, 13 May 2011 16:51:19 +0000
Message-ID: <1571128F4B736C42B743F492521F123B1EAB83@008-AM1MPN1-003.mgdnok.nokia.com>
References: <201105131337.p4DDbdao009901@cichlid.raleigh.ibm.com> <1571128F4B736C42B743F492521F123B1EAAB8@008-AM1MPN1-003.mgdnok.nokia.com> <201105131625.p4DGPiUT010897@cichlid.raleigh.ibm.com>
In-Reply-To: <201105131625.p4DGPiUT010897@cichlid.raleigh.ibm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.243.186.190]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 13 May 2011 16:51:21.0610 (UTC) FILETIME=[FCCA9EA0:01CC118D]
X-Nokia-AV: Clean
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 May 2011 16:51:49 -0000

> I also think that dealing with this issue in more detail may not be so easy, and it would be better to do that as updates to those documents (or a standalone 
>document).
>
> E.g., even DHCP by itself has a longstanding vagueness about how to handle the merging of information received from running DHCP on different interfaces. (And 
> one reason its hard is that if the two interfaces are in different management domains, there is no easy way to merge the information. We now have a separate WG 
> (MIF) dealing with that sort of thing.)

Agreed, and I don't think the Node Requirements doc is the place to provide this kind of clarification.

v2.23.0 | Report a Bug | By Email