IETF Logo Mail Archive

Re: [dispatch] Revised Proposed Session-ID Charter

"Dawes, Peter, VF-Group" <Peter.Dawes@vodafone.com> Tue, 21 February 2012 14:58 UTC

Return-Path: <Peter.Dawes@vodafone.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8086521F8857 for <dispatch@ietfa.amsl.com>; Tue, 21 Feb 2012 06:58:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Level:
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[AWL=0.600, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 WZZA+T5XkPOQ for <dispatch@ietfa.amsl.com>; Tue, 21 Feb 2012 06:58:12 -0800 (PST)
Received: from mailout02.vodafone.com (mailout02.vodafone.com [195.232.224.71]) by ietfa.amsl.com (Postfix) with ESMTP id 5BCFE21F884F for <dispatch@ietf.org>; Tue, 21 Feb 2012 06:58:12 -0800 (PST)
Received: from mailint02 (localhost [127.0.0.1]) by mailout02 (Postfix) with ESMTP id B12C72149E1 for <dispatch@ietf.org>; Tue, 21 Feb 2012 15:58:10 +0100 (CET)
Received: from avoexs04.internal.vodafone.com (avoexs04.dc-ratingen.de [145.230.4.198]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mailint02 (Postfix) with ESMTPS id 9DC65214977; Tue, 21 Feb 2012 15:58:10 +0100 (CET)
Received: from EITO-MBX02.internal.vodafone.com ([145.230.4.11]) by avoexs04.internal.vodafone.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 21 Feb 2012 15:57:44 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 21 Feb 2012 15:58:09 +0100
Message-ID: <C6A11A02FF1FBF438477BB38132E4741086FC406@EITO-MBX02.internal.vodafone.com>
In-Reply-To: <026901ccf003$8f063aa0$ad12afe0$@packetizer.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dispatch] Revised Proposed Session-ID Charter
Thread-Index: AQFuH+2Dh9+77xg5TjYrG8plMP4/MpcDxxpQgAFKkiA=
References: <C6A11A02FF1FBF438477BB38132E4741086FC1E8@EITO-MBX02.internal.vodafone.com> <026901ccf003$8f063aa0$ad12afe0$@packetizer.com>
From: "Dawes, Peter, VF-Group" <Peter.Dawes@vodafone.com>
To: "Paul E. Jones" <paulej@packetizer.com>, dispatch@ietf.org
X-OriginalArrivalTime: 21 Feb 2012 14:57:44.0083 (UTC) FILETIME=[2A8B8E30:01CCF0A9]
Subject: Re: [dispatch] Revised Proposed Session-ID Charter
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Tue, 21 Feb 2012 14:58:16 -0000

Hi Paul,
Thanks for reading the draft. It is expected (clause 6.) that the
configuration framework in RFC 6080 will be used with a profile type of
"User Profile", so subscription to d1.foocorp.com would be as below
(from RFC 6080).

Regards,
Peter

(RFC 6080)
5.1.4.3.  User Profile Type

   To create a Subscription URI to request the user profile on behalf of
   a user, the device needs to know the user's AoR.  This can be
   statically or dynamically configured on the device (e.g., user input,
   or propagated as part of the device profile).  Similar to device
   profiles, the content and propagation of user profiles may differ,
   based on deployment scenarios (i.e., users belonging to the same
   domain may -- or may not -- be provided the same profile).  To create
   a Subscription URI, the following rules apply:

Petrie & Channabasappa       Standards Track                   [Page 21]
RFC 6080               SIP Configuration Framework            March 2011

   o  The device MUST set the Request-URI to the user AoR.

   o  The device MUST populate the From field with the user AoR.

   An authoritative SIP proxy for a SIP provider's network that receives
   a profile enrollment request for the user profile type will route
   based on the Event Header field values, thus allowing a subscription
   to the user's AoR to be routed to the appropriate PDS.


-----Original Message-----
From: Paul E. Jones [mailto:paulej@packetizer.com] 
Sent: 20 February 2012 19:12
To: Dawes, Peter, VF-Group; dispatch@ietf.org
Cc: laura.liess.dt@googlemail.com
Subject: RE: [dispatch] Revised Proposed Session-ID Charter

Peter,

I looked over the draft quickly (so perhaps I missed it), but how does
Alice learn the address of d1.foocorp.com?

Paul

> -----Original Message-----
> From: Dawes, Peter, VF-Group [mailto:Peter.Dawes@vodafone.com]
> Sent: Monday, February 20, 2012 12:21 PM
> To: dispatch@ietf.org
> Cc: laura.liess.dt@googlemail.com; paulej@packetizer.com
> Subject: Re: [dispatch] Revised Proposed Session-ID Charter
> 
> Hello Laura, All,
> The topic of Session-ID has interest from both IETF, 3GPP, and the 
> Open Mobile Alliance (OMA) and I am keen to contribute to any new WG. 
> I have just re-submitted my session-id related draft to label it
"dispatch"
> (not "sipping" as previously).
> 
> http://datatracker.ietf.org/doc/draft-dawes-dispatch-debug/
> 
> To help track the various requirements and proposals, clause " 3.
> Related Drafts and Specifications" has been added with a list of other

> drafts (currently 5) and non-IETF specifications (currently 2) that I 
> am aware of related to this topic. I hope we can proceed soon with the
work.
> 
> Regards,
> Peter

v2.23.0 | Report a Bug | By Email