Re: [dhcwg] *DRAFT* dhc WG agenda

JiangSheng 66104 <shengjiang@huawei.com> Sat, 26 July 2008 20:47 UTC

Return-Path: <dhcwg-bounces@ietf.org>
X-Original-To: dhcwg-archive@megatron.ietf.org
Delivered-To: ietfarch-dhcwg-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2AE1B3A6987; Sat, 26 Jul 2008 13:47:05 -0700 (PDT)
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6F6293A6987; Sat, 26 Jul 2008 13:47:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level:
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_22=0.6]
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 TchLSVTlJiN6; Sat, 26 Jul 2008 13:47:01 -0700 (PDT)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211]) by core3.amsl.com (Postfix) with ESMTP id D0C603A6818; Sat, 26 Jul 2008 13:47:01 -0700 (PDT)
Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0K4M0028SSEI2I@usaga01-in.huawei.com>; Sat, 26 Jul 2008 13:47:07 -0700 (PDT)
Received: from huawei.com ([172.17.1.36]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0K4M00B2BSEG0K@usaga01-in.huawei.com>; Sat, 26 Jul 2008 13:47:06 -0700 (PDT)
Received: from [172.24.1.3] (Forwarded-For: [130.129.64.64]) by szxmc04-in.huawei.com (mshttpd); Sun, 27 Jul 2008 04:46:53 +0800
Date: Sun, 27 Jul 2008 04:46:53 +0800
From: JiangSheng 66104 <shengjiang@huawei.com>
In-reply-to: <488B3FD1.1010503@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
Message-id: <fdd6dcad12d6.12d6fdd6dcad@huawei.com>
MIME-version: 1.0
X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.14 (built Aug 8 2006)
Content-language: en
Content-disposition: inline
X-Accept-Language: en
Priority: normal
References: <DC113ED5-44B8-4F3E-87EE-EA3855C0B558@cisco.com> <4889C6F4.9070902@piuha.net> <f95bc2308556.8556f95bc230@huawei.com> <488B3FD1.1010503@piuha.net>
Cc: DHC WG <dhcwg@ietf.org>, Dhc Chairs <dhc-chairs@tools.ietf.org>, cga-ext@ietf.org, Csi Chairs <csi-chairs@tools.ietf.org>, Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] *DRAFT* dhc WG agenda
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org

Hi, Jari,

Please see my reply in lines.

Regards, Sheng

> You are right about how the charter text is written. However, I 
> have 
> been interpreting this a bit more broadly.
> 
> The other side is that the DHC charter also has a security item.

I guess we can have discussions in both WGs and see how it is going. In
CSI WG, we may focus on how CGA should be configured/generated in DHCP
environment; at the same time, in DHC WG,we may focus on more how DHCP
should be extended to adopt CGA.
 
> In any case, I do not think we can jump to solutions that involve 
> CGAs 
> without first doing the groundwork: what are the possible 
> approaches to 
> using CGAs in the conjunction of DHCP? Its hard to separate the use 
> of 
> CGA addresses in DHCP from the benefits to protecting the DHCP 
> process.

Between CGA and DHCP, there are actually two directions: a) using DHCP
to serve/enable the generation/usage of CGA on host, this should be the
work content of CSI; b) using CGA to serve the security of DHCP, this is
mainly about extend DHCP with new options, it should be work item of DHC.

> Please ask for the CSI slot as well and see where the discussion 
> takes us.

I did request a time slot in CSI to talk about the above a) point. I can
mention above b) point in my talk and clarify the different. Discussions
in both WG are useful to take these work forward.

Best regards,

Sheng
 
> JiangSheng 66104 wrote:
> > Hi, Jari,
> >
> > Yes, there is a DHCP relevant chartered item in CSI work group as I
> > quate below. However, it is quite different from this draft. The 
> chartered> item in CSI is mainly about how to use CGA in DHCP-
> managed networks. It is
> > covered by my another draft:
> > www.ietf.org/internet-drafts/draft-jiang-sendcgaext-cga-config-
> 02.txt>
> > The current CSI charter does not cover securing DHCP with CGA. 
> That's why I
> > submit this draft to DHC group. It is mainly adopting CGA to 
> serve DHCP
> > for security purpose. It is extension of DHCP, not extension of 
> CGA. I think
> > it is better to do this work in DHC WG rather than CSI. Based on 
> the above
> > understanding, I did not request a time slot in CSI
> >
> > "Develop an informational document analysing different approaches to
> > allow SeND and CGAs to be used in conjunction with DHCP, and making
> > recommendations on which are the best suited. Recharter based on the
> > result of the analysis."
> >
> > Best regards,
> >
> > Sheng
> >
> > ----- Original Message -----
> > From: Jari Arkko <jari.arkko@piuha.net>
> > Date: Friday, July 25, 2008 8:28 pm
> > Subject: Re: [dhcwg] *DRAFT* dhc WG agenda
> >
> >   
> >>> Secure DHCPv6 using CGA                         S. Jiang        
> 
> >>>       
> >> 10 
> >>     
> >>> minutes
> >>>   <draft-jiang-dhc-Secure-DHCPv6-00>
> >>>   Initial WG review; accept as WG work item?
> >>>       
> >> Note that we have another WG, CSI, whose charter has a work item 
> on 
> >> securing DHCP with CGA. Or to be more exact, producing first a 
> >> design 
> >> analysis before actually picking a solution.
> >>
> >> As a result, I don't think we want to adopt this document in the 
> >> DHC WG.
> >>
> >> But don't take this as a suggestion to avoid the discussion! The 
> >> discussion on the list has been useful, and we should also talk 
> >> about it 
> >> in the meeting. Has a slot been requested from CSI?
> >>
> >> Jari
> >>
> >>
> >> _______________________________________________
> >> dhcwg mailing list
> >> dhcwg@ietf.org
> >> https://www.ietf.org/mailman/listinfo/dhcwg
> >>
> >>     
> >
> >
> >   
> 
> 
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg