IETF Logo Mail Archive

Re: [dispatch] draft-winterbottom-dispatch-locparam

Paul Kyzivat <pkyzivat@alum.mit.edu> Thu, 16 July 2015 14:51 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1FDF1A00DC for <dispatch@ietfa.amsl.com>; Thu, 16 Jul 2015 07:51:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.035
X-Spam-Level:
X-Spam-Status: No, score=-0.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_37=0.6, J_CHICKENPOX_39=0.6, SPF_SOFTFAIL=0.665] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IMD8ghHcYazG for <dispatch@ietfa.amsl.com>; Thu, 16 Jul 2015 07:51:37 -0700 (PDT)
Received: from resqmta-ch2-07v.sys.comcast.net (resqmta-ch2-07v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:39]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E99B91A0364 for <dispatch@ietf.org>; Thu, 16 Jul 2015 07:51:21 -0700 (PDT)
Received: from resomta-ch2-10v.sys.comcast.net ([69.252.207.106]) by resqmta-ch2-07v.sys.comcast.net with comcast id t2pd1q0092JGN3p012rMqo; Thu, 16 Jul 2015 14:51:21 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-10v.sys.comcast.net with comcast id t2rL1q00j3Ge9ey012rMD4; Thu, 16 Jul 2015 14:51:21 +0000
Message-ID: <55A7C4E7.2090504@alum.mit.edu>
Date: Thu, 16 Jul 2015 10:51:19 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: dispatch@ietf.org
References: <1FDDC22B-849A-448D-AA1C-657064B84C55@gmail.com>
In-Reply-To: <1FDDC22B-849A-448D-AA1C-657064B84C55@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1437058281; bh=QT7X8Dz+hyItDyAA+urBhSXIjthzdD7ClStjkBnzfAc=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=XtB3ax3ZDXiSkQBrzpL8m5AGhIzIgImX0t/Hsn+WMl3O5EzTifkAY/KI3AqfFhbGn qaqO7QnnhAgVgCfEnOfyBQWNTN95cNJzgfW0oIgCGtS4XGkLkul7K3OOhlF1h71TpC u6LtVbFcc5zcWAY/qPgGTlh2paS33zM8Pvt9JJBeHEAwz9kh4cI02NnzL6NxsS7vcn DMOIsc/JYjpD71ovyYt/nrE70Evd/2jgu0i8NOn0FDBxPs5apIeTdKxs0iy+OjrYKM 5RWhjd5092Y3Gp1g/NoPik7CEsovQqH4ZsLwehFEENNbXfnf417TKRO+nWAx+8IdRK p9SNTwulRYTRQ==
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/6NRyz8RzyEUh9utaxD--WWg6yIg>
Subject: Re: [dispatch] draft-winterbottom-dispatch-locparam
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jul 2015 14:51:38 -0000

James,

I was just looking at this draft. I don't understand what assumptions it 
is making regarding trust model. Is this intended specifically for 3gpp 
and its trust model? Section 4 says:

    If a proxy receives a message
    from an untrusted source with the loc-src parameter set then it MUST
    remove the loc-src parameter before passing the message into a
    trusted network.

Are we assuming a Spec(t) as defined in 3325?

And is that enough? The obvious issue is the potential for somebody to 
lie about the location source.

Also, the location is specified as a 'host'. I assume you mean that as 
defined in 3261, where it is defined as:

   host = hostname / IPv4address / IPv6reference

Is it really meaningful to use an IP?

Is the expectation that the recipient will simply use these with a 
whitelist or blacklist to determine preferences? Or else how will it be 
used?

	Thanks,
	Paul

On 6/23/15 5:11 AM, James Winterbottom wrote:
> Hi All,
>
> I a notice about this draft a few weeks ago but haven’t seen and follow up discussion.
> This work is required in ETSI and I believe that as I understand from some 3GPP folks they would like something similar to this also.
>
> https://tools.ietf.org/html/draft-winterbottom-dispatch-locparam-00
>
> I am just not sure where the right final home for it is.
>
> Cheers
> James
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>

v2.14.0 | Report a Bug | By Email