IETF Logo Mail Archive

RE: [Manet-dt] IANA Port & Multicast Addresses

"Templin, Fred L" <Fred.L.Templin@boeing.com> Thu, 29 June 2006 21:09 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fw3ls-00008s-VK; Thu, 29 Jun 2006 17:09:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fw3lr-0008WV-Mn for manet-dt@ietf.org; Thu, 29 Jun 2006 17:09:55 -0400
Received: from slb-smtpout-01.boeing.com ([130.76.64.48] helo=slb-smtpout-01.ns.cs.boeing.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fw3lp-0004d0-Ba for manet-dt@ietf.org; Thu, 29 Jun 2006 17:09:55 -0400
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [192.42.227.216]) by slb-smtpout-01.ns.cs.boeing.com (8.13.6/8.13.6/TEST_SMTPIN) with ESMTP id k5TL5vPO015099; Thu, 29 Jun 2006 14:05:57 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id k5TL69w14083; Thu, 29 Jun 2006 14:06:09 -0700 (PDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 29 Jun 2006 14:06:08 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Manet-dt] IANA Port & Multicast Addresses
Date: Thu, 29 Jun 2006 14:06:08 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A1017740D7@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <44A418D2.8050008@dif.um.es>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Manet-dt] IANA Port & Multicast Addresses
Thread-Index: AcabqA3D48UDrqZ+Qm2Q3tnSOGPQLgAFx3Vg
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Pedro M. Ruiz" <pedrom@dif.um.es>
X-OriginalArrivalTime: 29 Jun 2006 21:06:08.0910 (UTC) FILETIME=[D7DA3AE0:01C69BBF]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: manet-dt@ietf.org
X-BeenThere: manet-dt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: MANET Design Team <manet-dt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/manet-dt>, <mailto:manet-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/manet-dt>
List-Post: <mailto:manet-dt@ietf.org>
List-Help: <mailto:manet-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/manet-dt>, <mailto:manet-dt-request@ietf.org?subject=subscribe>
Errors-To: manet-dt-bounces@ietf.org

Pedro,

>> An immediate use-case is for multicast
>> discovery of Internet gateways that are within the connected MANET
>> but multiple L3 hops away.	  
>
> Well, I think for that particular case, there might be better
> alternatives being evaluated within AUTOCONF WG... but I can
> still see other use-cases for this.

We have an AUTOCONF-related proposal that uses site-scoped
multicast for Internet gateway discovery:

http://www.ietf.org/internet-drafts/draft-templin-autoconf-dhcp-01.txt

What do the other alternatives being evaluated in AUTOCONF
do in terms of Internet gateway discovery?

Thanks - Fred
fred.l.templin@boeing.com

________________________________

From: Pedro M. Ruiz [mailto:pedrom@dif.um.es] 
Sent: Thursday, June 29, 2006 11:16 AM
To: Templin, Fred L
Cc: Dearlove, Christopher (UK); Ian Chakeres; manet-dt@ietf.org
Subject: Re: [Manet-dt] IANA Port & Multicast Addresses


Templin, Fred L wrote: 

			Chris, is your opinion we should define only one
link-local multicast
			address at this time?
			      

		I think we should find out what people want and submit
		whatever there's a definite need for (not a hypothetical
		maybe in the future case). I only can see a need for
		all link-local neighbour routers in terms of what the WG
		is chartered to do. If someone else has such a need (an
		aspect of SMF or DYMO I've overlooked for example) then
		bring that on too, but if not, not.
		    

	
	I would also like to see at least a site-scoped "All MANET
Routers"
	address to go with the link-local one, i.e., as for the "All
Routers"
	multicast address in IPv6.

Fully agree.


	 An immediate use-case is for multicast
	discovery of Internet gateways that are within the connected
MANET
	but multiple L3 hops away.
	  

Well, I think for that particular case, there might be better
alternatives being evaluated within AUTOCONF WG... but I can still see
other use-cases for this.

--Pedro


	Fred
	fred.l.templin@boeing.com 
	
	_______________________________________________
	Manet-dt mailing list
	Manet-dt@ietf.org
	https://www1.ietf.org/mailman/listinfo/manet-dt
	
	  



-- 
---------------------------------------------------------------------
Pedro M. Ruiz, Ph.D.                    E-mail: pedrom@dif.um.es
Fac. Informatica, Univ. of Murcia       Phone:  +34968364335
Campus de Espinardo s/n                 Fax:    +34968364151
E-30100, Espinardo, Murcia              www: ants.dif.um.es/~pedrom/
SPAIN
---------------------------------------------------------------------


_______________________________________________
Manet-dt mailing list
Manet-dt@ietf.org
https://www1.ietf.org/mailman/listinfo/manet-dt

v2.8.7 | Report a Bug | By Email