Re: [Ecrit] Requesting IETF LC for phonebcp - Minor IM issue

"Richard L. Barnes" <rbarnes@bbn.com> Tue, 08 February 2011 20:25 UTC

Return-Path: <rbarnes@bbn.com>
X-Original-To: ecrit@core3.amsl.com
Delivered-To: ecrit@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 32BA23A6857 for <ecrit@core3.amsl.com>; Tue, 8 Feb 2011 12:25:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 udQJPkBg+ZIt for <ecrit@core3.amsl.com>; Tue, 8 Feb 2011 12:25:44 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by core3.amsl.com (Postfix) with ESMTP id E6D5A3A672E for <ecrit@ietf.org>; Tue, 8 Feb 2011 12:25:42 -0800 (PST)
Received: from [128.89.252.183] (port=63205 helo=[10.242.10.142]) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.74 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1Pmu8D-000I2r-QB; Tue, 08 Feb 2011 15:25:50 -0500
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: "Richard L. Barnes" <rbarnes@bbn.com>
In-Reply-To: <1B44C0C7-C0BF-4FCF-93A9-08610F63DE84@brianrosen.net>
Date: Tue, 08 Feb 2011 14:25:46 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <EA7AE8AE-1D62-4796-927E-B5A10723BF20@bbn.com>
References: <C9101EEA-2E7A-4CA9-8A87-EF4BEA8E5E6B@nostrum.com> <201102072250.p17MoB5T019815@rcdn-core2-6.cisco.com>, <56B8D23B-9A04-4547-B144-EEEB77BF4AF8@nostrum.com>, <4D510CC4.2050605@omnitor.se> <BLU152-w48C46B1CB4D657561FCA9993EA0@phx.gbl> <1B44C0C7-C0BF-4FCF-93A9-08610F63DE84@brianrosen.net>
To: Brian Rosen <br@brianrosen.net>
X-Mailer: Apple Mail (2.1082)
Cc: ecrit@ietf.org
Subject: Re: [Ecrit] Requesting IETF LC for phonebcp - Minor IM issue
X-BeenThere: ecrit@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ecrit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ecrit>
List-Post: <mailto:ecrit@ietf.org>
List-Help: <mailto:ecrit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ecrit>, <mailto:ecrit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Feb 2011 20:25:45 -0000

<hat type="individual" />

(I saw this on the XMPP list first, so my extended reply is there.  I just sent it, so can't provide a link yet.)

I do not think we should add XMPP to phonebcp at this point.  Even though XMPP for emergency services is a great idea, it would not be a trivial addition.  Let's let phonebcp go to RFC and handle XMPP in an update.

--Richard




On Feb 8, 2011, at 9:14 AM, Brian Rosen wrote:

> Yes, I agree.
> 
> I'm certain we will have a rev due to LC comments, and I will fix the text in that rev.
> 
> concur with Bernard on xmpp.
> 
> Brian
> 
> On Feb 8, 2011, at 8:33 AM, Bernard Aboba wrote:
> 
>> I agree with this comment -- both should be required in the PSAP, not the endpoint. 
>> 
>> On XMPP support for emergency services, that is probably something
>> to bring to the XMPP WG (or the XSF).  The question will remain open
>> until there is documentation, either describing how it can be done, or
>> explaining why it is not supported.  Until then, phonebcp should probably
>> remain silent. 
>> 
>> 
>> > Date: Tue, 8 Feb 2011 10:28:36 +0100
>> > From: gunnar.hellstrom@omnitor.se
>> > To: ecrit@ietf.org
>> > Subject: Re: [Ecrit] Requesting IETF LC for phonebcp - Minor IM issue
>> > 
>> > I think I discussed a need for a minor change in September.
>> > 
>> > It is in the Media chapter 14.
>> > 
>> > This statement:
>> > "ED-75 Endpoints supporting Instant Messaging (IM) MUST support both 
>> > [RFC3428] and [RFC4975]."
>> > 
>> > It looks strange to require both IM protocols of the endpoint. Usually 
>> > they support one. The requirement would be suitable for a PSAP.
>> > 
>> > So, the agreement was to change to:
>> > 
>> > "ED-75 Endpoints supporting Instant Messaging (IM) MUST support either 
>> > [RFC3428] or [RFC4975]."
>> > 
>> > ( maybe there is now even an interest to add XMPP to that list, or do we 
>> > then open for a heap of complications regarding addressing and location 
>> > information etc. )
>> > 
>> > I do not regard this to be a subtantial issue, so I did not want to 
>> > bother the ietf mail list with it.
>> > 
>> > /Gunnar
>> > ------------------------------------------------------------------------
>> > >> At 04:37 PM 2/7/2011, Robert Sparks wrote:
>> > >>> All -
>> > >>>
>> > >>> I've requested IETFLC for the phonebcp draft. There are still some outstanding questions/comments from John Elwell that should be treated as last call comments.
>> > >>> Also, something needs to register the sos.*.test URNs. I think this document could do that.
>> > >>>
>> > >>> RjS
>> > >>> _______________________________________________
>> > >>> Ecrit mailing list
>> > >>> Ecrit@ietf.org
>> > >>> https://www.ietf.org/mailman/listinfo/ecrit
>> > > _______________________________________________
>> > > Ecrit mailing list
>> > > Ecrit@ietf.org
>> > > https://www.ietf.org/mailman/listinfo/ecrit
>> > _______________________________________________
>> > Ecrit mailing list
>> > Ecrit@ietf.org
>> > https://www.ietf.org/mailman/listinfo/ecrit
>> _______________________________________________
>> Ecrit mailing list
>> Ecrit@ietf.org
>> https://www.ietf.org/mailman/listinfo/ecrit
> 
> _______________________________________________
> Ecrit mailing list
> Ecrit@ietf.org
> https://www.ietf.org/mailman/listinfo/ecrit