IETF Logo Mail Archive

Re: [dhcwg] L2RA Clarification

"MILES DAVID" <David.Miles@alcatel-lucent.com.au> Wed, 25 March 2009 21:54 UTC

Return-Path: <David.Miles@alcatel-lucent.com.au>
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 AAFB43A68EF for <dhcwg@core3.amsl.com>; Wed, 25 Mar 2009 14:54:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.638
X-Spam-Level:
X-Spam-Status: No, score=-2.638 tagged_above=-999 required=5 tests=[AWL=-0.040, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 iiRmnDceTN9f for <dhcwg@core3.amsl.com>; Wed, 25 Mar 2009 14:54:45 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id 9D4553A63EB for <dhcwg@ietf.org>; Wed, 25 Mar 2009 14:54:45 -0700 (PDT)
Received: from ihrh1.emsr.lucent.com (h135-1-218-53.lucent.com [135.1.218.53]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id n2PLta6I010828; Wed, 25 Mar 2009 16:55:36 -0500 (CDT)
Received: from mail.apac.alcatel-lucent.com (h202-65-2-130.alcatel.com [202.65.2.130]) by ihrh1.emsr.lucent.com (8.13.8/emsr) with ESMTP id n2PLtYSv028877; Wed, 25 Mar 2009 16:55:35 -0500 (CDT)
Received: from sgsinsbhs02.ad4.ad.alcatel.com (sgsinsbhs02.ap.lucent.com [135.254.109.35]) by mail.apac.alcatel-lucent.com (8.13.7/8.13.7/Alcanet1.0) with ESMTP id n2PLshHs005799; Thu, 26 Mar 2009 05:54:43 +0800
Received: from SGSINSMBS02.ad4.ad.alcatel.com ([135.254.109.30]) by sgsinsbhs02.ad4.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 26 Mar 2009 05:55:32 +0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9AD94.6B729340"
Date: Thu, 26 Mar 2009 05:53:13 +0800
Message-ID: <986DCE2E44129444B6435ABE8C9E424D02F28AD6@SGSINSMBS02.ad4.ad.alcatel.com>
In-Reply-To: <D9872168DBD43A41BD71FFC4713274D406BCD36A@xmb-ams-33b.emea.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: L2RA Clarification
Thread-Index: AcmtkN8Q7tQ91VCKRaG+HTVgQKu36AAAuXuQAAAQZLA=
References: <986DCE2E44129444B6435ABE8C9E424D02F28AAD@SGSINSMBS02.ad4.ad.alcatel.com> <D9872168DBD43A41BD71FFC4713274D406BCD36A@xmb-ams-33b.emea.cisco.com>
From: MILES DAVID <David.Miles@alcatel-lucent.com.au>
To: "Wojciech Dec (wdec)" <wdec@cisco.com>, dhcwg@ietf.org, dhc Chairs <dhc-chairs@tools.ietf.org>
X-OriginalArrivalTime: 25 Mar 2009 21:55:32.0924 (UTC) FILETIME=[6BA0DFC0:01C9AD94]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 202.65.2.130
Subject: Re: [dhcwg] L2RA Clarification
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: <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, 25 Mar 2009 21:54:47 -0000

Chairs,

 

Can we take this (draft-ietf-dhc-l2ra-03) to WG last call on the list?

 

Cheers,

 

-David

 

From: Wojciech Dec (wdec) [mailto:wdec@cisco.com] 
Sent: Wednesday, March 25, 2009 2:52 PM
To: MILES DAVID; dhcwg@ietf.org
Subject: RE: L2RA Clarification

 

Agreed. I was reading
http://tools.ietf.org/html/draft-ietf-dhc-l2ra-extensions-01 during the
preso. Got no issues with draft-ietf-dhc-l2ra-03 

 

-Woj.

	 

	
________________________________


	From: MILES DAVID [mailto:David.Miles@alcatel-lucent.com.au] 
	Sent: 25 March 2009 14:30
	To: Wojciech Dec (wdec); dhcwg@ietf.org
	Subject: L2RA Clarification

	Woj,

	 

	I just checked the draft-ietf-dhc-l2ra-03 and there is nothing
in this draft I can see that is new/not per current implementation.

	 

	The Relay Agent Information Option (RFC 3046) is commonly known
as Option-82. It is not the option described in
draft-ietf-l2ra-extensions-01: this extensions draft defines a Relay
Agent Hardware Address which may be what you were thinking of.

	 

	This would lead me to ask the WG whether this we can progress
last call pending Woj's comments? Unfortunately the original agenda
linked the l2ra-extenions draft by mistake.

	 

	Cheers,

	 

	David Miles

v2.23.0 | Report a Bug | By Email