Re: [Geopriv] AD review: draft-ietf-geopriv-dhcp-lbyr-uri-option-11

"James M. Polk" <jmpolk@cisco.com> Mon, 03 October 2011 18:14 UTC

Return-Path: <jmpolk@cisco.com>
X-Original-To: geopriv@ietfa.amsl.com
Delivered-To: geopriv@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63BB121F8D2C for <geopriv@ietfa.amsl.com>; Mon, 3 Oct 2011 11:14:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.248
X-Spam-Level:
X-Spam-Status: No, score=-103.248 tagged_above=-999 required=5 tests=[AWL=-0.649, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FtIPdBVanK98 for <geopriv@ietfa.amsl.com>; Mon, 3 Oct 2011 11:14:32 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id D031721F8D2B for <geopriv@ietf.org>; Mon, 3 Oct 2011 11:14:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jmpolk@cisco.com; l=2863; q=dns/txt; s=iport; t=1317665856; x=1318875456; h=message-id:date:to:from:subject:cc:in-reply-to: references:mime-version:content-transfer-encoding; bh=xqUTNdHYt+2CykmKA0mJd5bwkX1rDRO6F3KtZdOQgQg=; b=KxOqoFHz3wK9QXcjijySjMgFcS7xhTZqUfal/zEugWjYEqIv2iRqzYuB tBSUcM4b2dX+EC9KR4BlyuDHI72oBphGbFpCG3nLt7OrX+eWjfczTSVr9 9Y+DlOMnWcRqb2wcVFGEoZ6o9+WxVZtsisHnrsvL69KAWzceg1yRTdXm8 E=;
X-IronPort-AV: E=Sophos;i="4.68,480,1312156800"; d="scan'208";a="5671497"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-2.cisco.com with ESMTP; 03 Oct 2011 18:17:35 +0000
Received: from jmpolk-wxp01.cisco.com (rcdn-jmpolk-8717.cisco.com [10.99.80.24]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p93IHYC1023691; Mon, 3 Oct 2011 18:17:34 GMT
Message-Id: <201110031817.p93IHYC1023691@mtv-core-4.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 03 Oct 2011 13:17:33 -0500
To: Ben Campbell <ben@nostrum.com>, Robert Sparks <rjsparks@nostrum.com>
From: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <1F890203-8CAD-44FE-84A6-137373D9CE19@nostrum.com>
References: <05398170-17BE-4A89-95A0-8850C5A8026C@nostrum.com> <201109150318.p8F3IgxP005025@mtv-core-1.cisco.com> <8DE85F29-D27B-4DF6-872E-E3DBB4B57774@nostrum.com> <7CD33531-AA74-405F-AC61-801DE7AFED82@nostrum.com> <EC041866-A02C-43E4-83A2-5D6A96DADD06@nostrum.com> <1F890203-8CAD-44FE-84A6-137373D9CE19@nostrum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Cc: geopriv@ietf.org, "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [Geopriv] AD review: draft-ietf-geopriv-dhcp-lbyr-uri-option-11
X-BeenThere: geopriv@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Geographic Location/Privacy <geopriv.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/geopriv>, <mailto:geopriv-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/geopriv>
List-Post: <mailto:geopriv@ietf.org>
List-Help: <mailto:geopriv-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/geopriv>, <mailto:geopriv-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Oct 2011 18:14:33 -0000

At 04:54 PM 9/22/2011, Ben Campbell wrote:
>I tend to agree with StPeter on the "pres" part. 
>But, I think there's still two issues--one I 
>already mentioned, and a possible new one:
>
>1) If you get an XMPP (address, or URI), what 
>are you going to do with it? The following guidance:
>
>"Responses to requests for URIs with other 
>schemes ("sip", "sips", "http", and "https") 
>MUST have MIME type 'application/pidf+xml'."
>
>… is not applicable "out of the box" to XMPP. It 
>needs quite a bit more elaboration. I'm okay 
>with making that "for future study", but it 
>would at least need to be called out separately.

hmm... this seems more complicated by the minute


>2) If you get a "pres" URI and allow it to 
>resolve to either SIP(s) or XMPP, how do you select which?

SIP Location Conveyance has a mechanism on how to 
pick between the SIP group (sip, sips, pres) and 
the http group (http, https), so if #2 allows a 
pick between sip and pres, there is a way to pick 
sip(s) (or pres).  There is no means to pick xmpp 
in SIP Location Conveyance though... to get this, 
we would have to create a new SIP option tag for 
the choice, and then use (i.e., follow) the 
existing mechanism in Location Conveyance. That 
should work with, i.e., it's pretty straightforward.


>On Sep 22, 2011, at 4:27 PM, Robert Sparks wrote:
>
> > So I IMed with StPeter - his reaction is "someone's implemented pres:?"
> >
> > Anyhow, my suggestion for now is to say "See 
> RFC3922 for using the pres: URI with XMPP" and I'll make sure
> > we get good review of that during last call.

BTW - I copied this quoted line and added the normative reference.

James


> >
> > RjS
> >
> > On Sep 22, 2011, at 3:38 PM, Ben Campbell wrote:
> >
> >> On Sep 22, 2011, at 3:12 PM, Robert Sparks wrote:
> >>
> >>> Ben -
> >>>
> >>> Can we tap your SIMPLE/XMPP guidance to 
> help us wrestle with the following point in 
> draft-ietf-geopriv-dhcp-lbyr-uri-option?
> >>>
> >>> On Sep 14, 2011, at 10:18 PM, James M. Polk wrote:
> >>> <snip/>
> >>>
> >>>>
> >>>>> 8) Why does section 3.3 rule out the use of XMPP with pres: URIs?
> >>>>
> >>>> huh... don't know...? What's the RFC I 
> should point at for this? Is it 5122?
> >>>>
> >>>
> >>> I think the right place to point might be 
> RFC3922 - is there a better one?
> >>
> >> 3922 is what you want for converting a 
> "pres" URI to an XMPP address. 5122 is what you 
> want if you want to include a "native" XMPP 
> URI. (Keep in mind, XMPP does not really use URIs natively)
> >>
> >> The bigger question to me is, can you 
> dereference an XMPP address and expect it to do 
> the right thing for a location URI? If so, how--is that documented somewhere?
> >>
> >>>
> >>> RjS
> >