Re: [Sipping] Examples in draft-ietf-sipping-config-framework-15
"Francois Audet" <audet@nortel.com> Tue, 24 March 2009 18:24 UTC
Return-Path: <AUDET@nortel.com>
X-Original-To: sipping@core3.amsl.com
Delivered-To: sipping@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 270773A68B4 for <sipping@core3.amsl.com>; Tue, 24 Mar 2009 11:24:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.981
X-Spam-Level:
X-Spam-Status: No, score=-5.981 tagged_above=-999 required=5 tests=[AWL=0.619, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 gooQNz0qvAml for <sipping@core3.amsl.com>; Tue, 24 Mar 2009 11:24:45 -0700 (PDT)
Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by core3.amsl.com (Postfix) with ESMTP id 054863A698E for <sipping@ietf.org>; Tue, 24 Mar 2009 11:24:44 -0700 (PDT)
Received: from zrc2hxm0.corp.nortel.com (zrc2hxm0.corp.nortel.com [47.103.123.71]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id n2OIPSq21424 for <sipping@ietf.org>; Tue, 24 Mar 2009 18:25:29 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 24 Mar 2009 13:25:11 -0500
Message-ID: <1ECE0EB50388174790F9694F77522CCF1D082350@zrc2hxm0.corp.nortel.com>
In-Reply-To: <1237918740.5485.27.camel@victoria-pingtel-com.us.nortel.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sipping] Examples in draft-ietf-sipping-config-framework-15
Thread-Index: AcmsrRELtq259istSTaxrzkwMYRqbAAALvYA
References: <1237918740.5485.27.camel@victoria-pingtel-com.us.nortel.com>
From: Francois Audet <audet@nortel.com>
To: Dale Worley <dworley@nortel.com>, SIPPING <sipping@ietf.org>
Subject: Re: [Sipping] Examples in draft-ietf-sipping-config-framework-15
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipping>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Mar 2009 18:24:46 -0000
I think you are correct. It should normally be the same. > -----Original Message----- > From: sipping-bounces@ietf.org > [mailto:sipping-bounces@ietf.org] On Behalf Of Worley, Dale > (BL60:9D30) > Sent: Tuesday, March 24, 2009 11:19 > To: SIPPING > Subject: [Sipping] Examples in draft-ietf-sipping-config-framework-15 > > I've been looking at the examples in > draft-ietf-sipping-config-framework-15, and I suspect that > one is not correct. Specifically, in section 7.1 is: > > SUBSCRIBE sip:urn%3auuid%3a00000000-0000-1000-0000-00FF8D82EDCB > @example.com SIP/2.0 > Event: ua-profile;profile-type=device;vendor="vendor.example.net"; > model="Z100";version="1.2.3"; > From: anonymous@example.com;tag=1234 > To: > sip:urn%3auuid%3a00000000-0000-1000-0000-00FF8D82EDCB@example.com > Call-ID: 3573853342923422@192.0.2.44 > CSeq: 2131 SUBSCRIBE > Contact: sip:urn%3auuid%3a00000000-0000-1000-0000-00FF8D82EDCB > @192.168.1.44 > ;+sip.instance="<urn:uuid:00000000-0000-0000-0000-123456789AB0>" > ;schemes="http,https" > Via: SIP/2.0/TCP 192.0.2.41; > branch=z9hG4bK6d6d35b6e2a203104d97211a3d18f57a > Accept: message/external-body, application/x-z100-device-profile > Content-Length: 0 > > As far as I can tell, 5.1.4.2, the user part of the > request-URI must be the "device identifier", which would be > in this case "urn:uuid:00000000-0000-1000-0000-00FF8D82EDCB". > The +sip.instance parameter of the Contact field must be the > same as that in the local network profile SUBSCRIBE request, > which 5.1.4.1 refers to sip-outbound. > > But it seems to me that the +sip.instance value is expected > to be the device identifier. And yet, in this example, it is > different from the device identifier in the request URI. I > suspect that I'm not understanding the concept behind this. > > Dale > > > _______________________________________________ > Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping > This list is for NEW development of the application of SIP > Use sip-implementors@cs.columbia.edu for questions on current > sip Use sip@ietf.org for new developments of core SIP >
- [Sipping] Examples in draft-ietf-sipping-config-f… Dale Worley
- [Sipping] Examples in draft-ietf-sipping-config-f… Dale Worley
- Re: [Sipping] Examples in draft-ietf-sipping-conf… Francois Audet