Re: [Ieprep] on the ieprep charter

ken carlberg <carlberg@g11.org.uk> Fri, 28 July 2006 03:27 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G6J0S-0004lT-9N; Thu, 27 Jul 2006 23:27:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G6J0R-0004jo-Qn for ieprep@ietf.org; Thu, 27 Jul 2006 23:27:19 -0400
Received: from athena.hosts.co.uk ([212.84.175.19]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G6J0Q-0003gm-HI for ieprep@ietf.org; Thu, 27 Jul 2006 23:27:19 -0400
Received: from [69.138.71.89] (helo=[192.168.1.2]) by athena.hosts.co.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.60) (envelope-from <carlberg@g11.org.uk>) id 1G6J0K-0004yj-74; Fri, 28 Jul 2006 04:27:14 +0100
In-Reply-To: <DBC1A7C7-9F3C-4557-A7BC-E081C482A5C3@cisco.com>
References: <44B4F17B.70105@jhuapl.edu> <80703C4C-C585-4601-9518-270A3A6A49CC@cisco.com> <44C9089E.3050802@jhuapl.edu> <B8C892A4-F711-4928-8EDA-FD7E717B702F@cisco.com> <44C9160F.1060001@jhuapl.edu> <DBC1A7C7-9F3C-4557-A7BC-E081C482A5C3@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <4594B807-4EDB-45A4-B2FB-0DCD30E7C3FC@g11.org.uk>
Content-Transfer-Encoding: 7bit
From: ken carlberg <carlberg@g11.org.uk>
Subject: Re: [Ieprep] on the ieprep charter
Date: Thu, 27 Jul 2006 23:27:06 -0400
To: Fred Baker <fred@cisco.com>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: -1.4 (-)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc: "Robert G. Cole" <robert.cole@jhuapl.edu>, ieprep@ietf.org
X-BeenThere: ieprep@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Internet Emergency Preparedness Working Group <ieprep.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ieprep@ietf.org>
List-Help: <mailto:ieprep-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ieprep>, <mailto:ieprep-request@ietf.org?subject=subscribe>
Errors-To: ieprep-bounces@ietf.org

> What the charter should, perhaps, address, is the status of  
> multicast in this. We all agree we need unicast solutions. RSVP  
> assumes that multicast is also a requirement, while NSIS presumes  
> that it can be summarily set aside. In civilian networks where  
> multicast is not widely deployed as a service, the point may be  
> moot. I am told that in your organization and others in coalition  
> with it, there are places where multicast is the predominant  
> traffic type, however. So we have to decide whether we need to  
> address that.

I'll chime up and say we *definitely* need to address multicast.  its  
fundamental in the context of efficiently supporting push-to-talk  
applications as one pushes IP further into the infrastructure of Land  
Mobile Radio.  and the subject becomes more of a headache since the  
establishment of talk groups are not based on explicitly signaled CAC

-ken


_______________________________________________
Ieprep mailing list
Ieprep@ietf.org
https://www1.ietf.org/mailman/listinfo/ieprep