RE: [Manet-dt] Revivied discussion on MANET multicast addresses

"Joe Macker" <joseph.macker@nrl.navy.mil> Fri, 19 May 2006 20:24 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FhBWM-0003QL-EP; Fri, 19 May 2006 16:24:26 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FhBWK-0003Q1-W0 for manet-dt@ietf.org; Fri, 19 May 2006 16:24:24 -0400
Received: from s2.itd.nrl.navy.mil ([132.250.83.3]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FhBWI-0002Q1-Ml for manet-dt@ietf.org; Fri, 19 May 2006 16:24:24 -0400
Received: from smtp.itd.nrl.navy.mil (smtp.itd.nrl.navy.mil [132.250.86.3]) by s2.itd.nrl.navy.mil (8.13.6+Sun/8.12.8) with SMTP id k4JKO6K3026388; Fri, 19 May 2006 16:24:10 -0400 (EDT)
Received: (from SEXTANT [132.250.92.22]) by smtp.itd.nrl.navy.mil (SMSSMTP 4.1.12.43) with SMTP id M2006051916240929987 ; Fri, 19 May 2006 16:24:09 -0400
From: "Joe Macker" <joseph.macker@nrl.navy.mil>
To: "'Ian Chakeres'" <ian.chakeres@gmail.com>, "'Templin, Fred L'" <Fred.L.Templin@boeing.com>
Subject: RE: [Manet-dt] Revivied discussion on MANET multicast addresses
Date: Fri, 19 May 2006 16:24:09 -0400
Message-ID: <028401c67b82$2f0b6a40$165cfa84@SEXTANT>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
In-Reply-To: <374005f30605161711x15b2d250v941a8d5b2eb48273@mail.gmail.com>
Thread-Index: AcZ5SKKl3XOzYb+iQkqf43lANC6YQACOIDZg
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
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

Well since we put such a notion in the SMF draft I am a fan. 
I don't believe it needs to be one address. It could be a range of
administratively scoped addresses. 

>-----Original Message-----
>From: Ian Chakeres [mailto:ian.chakeres@gmail.com] 
>Sent: Tuesday, May 16, 2006 8:12 PM
>To: Templin, Fred L
>Cc: manet-dt@ietf.org
>Subject: Re: [Manet-dt] Revivied discussion on MANET multicast 
>addresses
>
>How do people feel about defining one "site" scoped multicast 
>for manet protocols? Please write with support or dissent.
>
>I think the semantics for these multicast messages would be 
>that MANET routers must not  forwarded these packets out 
>non-manet interfaces.
>
>Ian
>
>On 5/16/06, Templin, Fred L <Fred.L.Templin@boeing.com> wrote:
>> > Unfortunately, things don't seem quite so clear-cut in IPv4.
>>
>> Then again, there is the IPv4 "Administratively Scoped"
>> multicast block (239.0.0.0/8) and portions of that space are 
>> designated as "Site-Local Scope"; see RFC2365 and:
>>
>> http://www.iana.org/assignments/multicast-addresses
>>
>> Fred
>> fred.l.templin@boeing.com
>>
>
>_______________________________________________
>Manet-dt mailing list
>Manet-dt@ietf.org
>https://www1.ietf.org/mailman/listinfo/manet-dt
>



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