[dhcwg] FW: Discussion of draft-ietf-dhc-l2ra-01.txt prior to dhc WG last call
Bharat Joshi <bharat_joshi@infosys.com> Thu, 18 September 2008 05:14 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 9FD423A6A17; Wed, 17 Sep 2008 22:14:59 -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 537DA3A68A1 for <dhcwg@core3.amsl.com>; Wed, 17 Sep 2008 22:14:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.381
X-Spam-Level:
X-Spam-Status: No, score=-0.381 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, RELAY_IS_220=2.118]
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 AIpLrdPAtEca for <dhcwg@core3.amsl.com>; Wed, 17 Sep 2008 22:14:57 -0700 (PDT)
Received: from Kecgate03.infosys.com (kecgate03.progeon.com [220.227.179.21]) by core3.amsl.com (Postfix) with ESMTP id A01693A6A17 for <dhcwg@ietf.org>; Wed, 17 Sep 2008 22:14:56 -0700 (PDT)
X-TM-IMSS-Message-ID: <00281bc200000c22@infosys.com>
Received: from blrkechub02.ad.infosys.com ([10.66.236.42]) by infosys.com ([220.227.179.21]) with ESMTP (TREND IMSS SMTP Service 7.0; TLS: TLSv1/SSLv3,128bits,RC4-MD5) id 00281bc200000c22 ; Thu, 18 Sep 2008 10:36:50 +0530
Received: from BLRKECMBX02.ad.infosys.com ([10.66.236.22]) by blrkechub02.ad.infosys.com ([10.66.236.42]) with mapi; Thu, 18 Sep 2008 10:34:08 +0530
From: Bharat Joshi <bharat_joshi@infosys.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Date: Thu, 18 Sep 2008 10:33:01 +0530
Thread-Topic: [dhcwg] Discussion of draft-ietf-dhc-l2ra-01.txt prior to dhc WG last call
Thread-Index: AckZA8+RBoxAJD1HRseYLHLnq4Q7GQAPvjAkAAJC2Gc=
Message-ID: <31D55C4D55BEED48A4459EB64567589A0C95C7D8FF@BLRKECMBX02.ad.infosys.com>
References: <46EDFFB40E4ABC4BB72D47CF34B186E30C84900A1B@BLRKECMBX02.ad.infosys.com> <31D55C4D55BEED48A4459EB64567589A0C95C7D8FB@BLRKECMBX02.ad.infosys.com>, <8E8BCEF6-E08F-43C5-9091-AF6E056A3211@nominum.com>, <31D55C4D55BEED48A4459EB64567589A0C95C7D8FD@BLRKECMBX02.ad.infosys.com>
In-Reply-To: <31D55C4D55BEED48A4459EB64567589A0C95C7D8FD@BLRKECMBX02.ad.infosys.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
Subject: [dhcwg] FW: Discussion of draft-ietf-dhc-l2ra-01.txt prior to dhc WG last call
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 All, Here are some suggestions received from Ted with my replies. Thanks, Bharat ------------------------------------------------------------------ From: Ted Lemon [Ted.Lemon@nominum.com] Sent: Thursday, September 18, 2008 1:57 AM To: Bharat Joshi Cc: pavan_kurapati Subject: Re: [dhcwg] Discussion of draft-ietf-dhc-l2ra-01.txt prior to dhc WG last call Sorry, the notes were on my OLPC, which I don't normally use when I'm at home, so I kept meaning to fetch them and then getting sidetracked. This is what I wrote in my notes when I reviewed it: l2ra It seems broken that the relay agents broadcast the DHCP message on all ports - that's revealing information to subscribers about each other that needn't be revealed. <Bharat> A normal layer 2 switch [acting as relay agen as well] may not be configured with a Up-link port or a port which leads to the router. In this case, it needs to broadcast the DHCP message on all ports. We included this in the text to show the need and importance of identifying the Up-Link port. </Bharat> 4.1.1 seems to go into too much detail about the actual DHCP protocol. <Bharat> We had started with minimal set of explanation but few internal reviewers and one external reviewer specifically asked few questions because of which we end up explaning everything here. I think this way it looks complete and does not left anything question open. </Bharat> 4.1.2, part 2, DHCP reply messages sounds like a protocol message. It would be better to say "in responses to unicast messages from the client". <Bharat> Yes. I can fix this. </Bharat> 4.2.2 seems broken. Not sure what to do here - the proposed solution is probably least likely to break badly. <Bharat> I did not get your point here. We have mentioned the issues due to introduction of L2 RA. Did you see any issue with the text here? </Bharat> Mostly the draft seems way too verbose. You have to read it closely to see all the issues that are brought out. It might be more readable/usable if as much repetition of information from the DHCP protocol spec as possible were removed. <Bharat> As mentioned above, this was done mostly to not leave any open question on how L2 RA handle a specific message. Let me look at it again and will try to remove some obvious things. </Bharat> **************** CAUTION - Disclaimer ***************** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS******** End of Disclaimer ********INFOSYS*** _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Discussion of draft-ietf-dhc-l2ra-01.txt … Ralph Droms
- [dhcwg] FW: Discussion of draft-ietf-dhc-l2ra-01.… Bharat Joshi
- Re: [dhcwg] FW: Discussion of draft-ietf-dhc-l2ra… Ted Lemon
- Re: [dhcwg] FW: Discussion of draft-ietf-dhc-l2ra… Bharat Joshi