[Sipping] RE: [Sip] SIP support for IN services
"Peterson, Jon" <jon.peterson@neustar.biz> Tue, 23 April 2002 07:33 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA08430 for <sipping-archive@odin.ietf.org>; Tue, 23 Apr 2002 03:33:00 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id DAA05794 for sipping-archive@odin.ietf.org; Tue, 23 Apr 2002 03:33:02 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA04516; Tue, 23 Apr 2002 03:16:37 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA04486 for <sipping@optimus.ietf.org>; Tue, 23 Apr 2002 03:16:34 -0400 (EDT)
Received: from oak.neustar.com (oak.neustar.com [209.173.53.70]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA08238 for <sipping@ietf.org>; Tue, 23 Apr 2002 03:16:31 -0400 (EDT)
Received: from chiimc01.il.neustar.com (stih650b-s1p2.va.neustar.com [209.173.53.65]) by oak.neustar.com (8.11.0/8.11.0) with ESMTP id g3N7G1H24680; Tue, 23 Apr 2002 03:16:01 -0400
Received: by chiimc01.il.neustar.com with Internet Mail Service (5.5.2653.19) id <J25ZMCL8>; Tue, 23 Apr 2002 02:15:56 -0500
Message-ID: <70565611B164D511957A001083FCDD5601870251@va02.va.neustar.com>
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: "'Vijay K. Gurbani'" <vkg@lucent.com>, SIPPING LIST <sipping@ietf.org>
Date: Tue, 23 Apr 2002 02:15:50 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Subject: [Sipping] RE: [Sip] SIP support for IN services
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
X-BeenThere: sipping@ietf.org
Trimming the distribution back to the SIPPING list. I have one comment off the bat - have you compared this work at all to the following draft: http://www.ietf.org/internet-drafts/draft-ietf-sipping-isup-01.txt As you may know, this draft is a SIPPING WG last item, and it is currently past WGLC. It contains, among other things, a SIP response code to Q.850 cause code mapping similar to the one in Appendix A of your document. However, there are some discrepancies between the mappings suggested by the two documents (it looks like yours may have been influenced by an earlier version of sipping-isup?). The mappings in the SIPPING-ISUP draft have been subjected to a reasonable amount of public scrutiny over the last two years or so, and I feel they tell a reasonably good story at this point. Some of the mappings in your draft look a little misplaced to me - to pick an example at random, '403 Forbidden' mapping to '1 Unallocated number'. I would actually suggest that your SIN draft should refer normatively to SIPPING-ISUP for this mapping and any other SIP-to-ISUP needs. Jon Peterson NeuStar, Inc. > -----Original Message----- > From: Vijay K. Gurbani [mailto:vkg@lucent.com] > Sent: Friday, April 19, 2002 8:24 AM > To: SIP LIST; SIPPING LIST; SPIRITS list; pint@lists.bell-labs.com > Subject: [Sip] SIP support for IN services > > > Folks: > > Enclosed is an I-D for review that describes SIP support for IN > services. The I-D represents agreement of the IETF SIN > (SIP/IN) design > team and is intended for publication as an informational RFC. It has > been through Last Call in the IETF SIN DT and the comments of the WGs > identified in the To list of this email are now being solicited. > > http://search.ietf.org/internet-drafts/draft-gurbani-sin-00.txt > > Thanks, > > - vijay > -- > Vijay K. Gurbani vkg@{lucent.com,research.bell-labs.com,acm.org} > Wireless Networks Group/Internet Software and eServices > Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440 > Naperville, Illinois 60566 Voice: +1 630 224 0216 > > > _______________________________________________ > Sip mailing list https://www1.ietf.org/mailman/listinfo/sip > This list is for NEW development of the core SIP Protocol > Use sip-implementors@cs.columbia.edu for questions on current sip > Use sipping@ietf.org for new developments on the application of sip > _______________________________________________ Sipping mailing list https://www1.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] SIP support for IN services Vijay K. Gurbani
- [Sipping] RE: [Sip] SIP support for IN services Peterson, Jon
- [Sipping] Re: [Sip] SIP support for IN services Vijay K. Gurbani
- Re: [Sipping] SIP support for IN services Jonathan Rosenberg
- Re: [Sipping] SIP support for IN services Vijay K. Gurbani
- Re: [Sipping] SIP support for IN services Jonathan Rosenberg
- Re: [Sipping] SIP support for IN services Vijay K. Gurbani
- Re: [Sipping] SIP support for IN services Jonathan Rosenberg
- Re: [Sipping] SIP support for IN services Vijay K. Gurbani