IETF Logo Mail Archive

Re: [dhcwg] Call for Adoption: draft-yeh-dhc-dhcpv6-prefix-pool-opt-08

zhou.sujing@zte.com.cn Wed, 05 September 2012 03:36 UTC

Return-Path: <zhou.sujing@zte.com.cn>
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 1F7A211E80D3; Tue, 4 Sep 2012 20:36:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.526
X-Spam-Level:
X-Spam-Status: No, score=-98.526 tagged_above=-999 required=5 tests=[AWL=3.772, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, 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 QrEey8Dt2f1c; Tue, 4 Sep 2012 20:36:11 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id 0AE6911E80BA; Tue, 4 Sep 2012 20:36:10 -0700 (PDT)
Received: from [192.168.168.119] by mx5.zte.com.cn with surfront esmtp id 10723543655668; Wed, 5 Sep 2012 11:18:39 +0800 (CST)
Received: from mse02.zte.com.cn (unknown [10.30.3.21]) by Websense Email Security Gateway with ESMTPS id 40EA972CDF5; Wed, 5 Sep 2012 11:32:03 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id q853a0GO071709; Wed, 5 Sep 2012 11:36:00 +0800 (GMT-8) (envelope-from zhou.sujing@zte.com.cn)
In-Reply-To: <B5C1848E-EFDD-46BF-8601-8EAF55A41E48@employees.org>
To: Ole Trøan <otroan@employees.org>
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF3CEC0CC7.27F371E6-ON48257A70.00135582-48257A70.0013D6B6@zte.com.cn>
From: zhou.sujing@zte.com.cn
Date: Wed, 05 Sep 2012 11:35:53 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2012-09-05 11:35:57, Serialize complete at 2012-09-05 11:35:57
Content-Type: multipart/alternative; boundary="=_alternative 0013D6B548257A70_="
X-MAIL: mse02.zte.com.cn q853a0GO071709
Cc: dhcwg@ietf.org, dhcwg-bounces@ietf.org
Subject: Re: [dhcwg] Call for Adoption: draft-yeh-dhc-dhcpv6-prefix-pool-opt-08
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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, 05 Sep 2012 03:36:12 -0000

But the prefix pool transfer between DHCP server and DHCP Relay also needs 
to be authenticated. 

> 
> >> does this work with DHCPv6 authentication?
> > It doesn't affect it at all. Servers that auhenticate their responses
> > are signing REPLY message that is in turn encapsulated in RELAY-REPL.
> > THe prefix-pool option is insterted in RELAY-REPL and the REPLY inside
> > is never modified. prefix-pool never reaches the client. If that is 
was
> > your impression after reading the draft, perhaps it should be 
clarified
> > in the text?
> 
> ah, I see. I must have missed that in the text. I see there is a MAY in 
3315.
> 
> cheers,
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg

v2.26.15 | Report a Bug | By Email | System Status