[Sip] Compact forms questions
Kosta Koeman <kkoeman@techemail.com> Thu, 06 June 2002 01:41 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 VAA04774 for <sip-archive@odin.ietf.org>; Wed, 5 Jun 2002 21:41:51 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id VAA16785 for sip-archive@odin.ietf.org; Wed, 5 Jun 2002 21:42:21 -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 VAA14974; Wed, 5 Jun 2002 21:16:04 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id VAA14943 for <sip@ns.ietf.org>; Wed, 5 Jun 2002 21:16:01 -0400 (EDT)
Received: from omta04.mta.everyone.net (sitemail3.everyone.net [216.200.145.37]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA03214 for <sip@ietf.org>; Wed, 5 Jun 2002 21:15:31 -0400 (EDT)
Received: from sitemail.everyone.net (dsnat [216.200.145.62]) by omta04.mta.everyone.net (Postfix) with ESMTP id C9CB9502BF for <sip@ietf.org>; Wed, 5 Jun 2002 18:16:00 -0700 (PDT)
Received: by sitemail.everyone.net (Postfix, from userid 99) id A4EE236F9; Wed, 5 Jun 2002 18:16:00 -0700 (PDT)
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0
X-Mailer: MIME-tools 5.41 (Entity 5.404)
Date: Wed, 05 Jun 2002 18:16:00 -0700
From: Kosta Koeman <kkoeman@techemail.com>
To: sip@ietf.org
Reply-To: kkoeman@techemail.com
X-Originating-Ip: [207.46.137.9]
Message-Id: <20020606011600.A4EE236F9@sitemail.everyone.net>
Content-Transfer-Encoding: 7bit
Subject: [Sip] Compact forms questions
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Session Initiation Protocol <sip.ietf.org>
X-BeenThere: sip@ietf.org
Content-Transfer-Encoding: 7bit
I've noted the following list from http://www.iana.org/assignments/sip-parameters that summarizes the compact forms defined for SIP (note: I have removed all header names without a compact form). Allow-Events u [RFCevents] <draft-ietf-sip-events-05.txt> Call-ID i [RFC2543], draft-ietf-sip-rfc2543bis Contact m [RFC2543], draft-ietf-sip-rfc2543bis Content-Encoding e [RFC2543], draft-ietf-sip-rfc2543bis Content-Length l [RFC2543], draft-ietf-sip-rfc2543bis Content-Type c [RFC2543], draft-ietf-sip-rfc2543bis Event o [RFCevent] <draft-ietf-sip-events-05.txt> From f [RFC2543], draft-ietf-sip-rfc2543bis Subject s [RFC2543], draft-ietf-sip-rfc2543bis Supported k draft-ietf-sip-rfc2543bis To t [RFC2543], draft-ietf-sip-rfc2543bis Via v [RFC2543], draft-ietf-sip-rfc2543bis So the compact forms u & o are defined in the SIP-Specific Event Notification draft; i, m, e, l, c, o, f, s, t, & v are defined in the SIP spec/draft. I could not find the exact document where the compact form k was defined (besides the list, of course). What about the compact forms, r (Refer-To) and b (Referred-By), respectively defined in "The Refer Method" draft (draft-ietf-sip-refer-04) and "The Referred-By Mechanism" draft (draft-ietf-sip-referredby-00)? Are these compact forms not included in the list above due to the fact that their respective documents have not been submitted to be published as proposed standards? Since these compact forms have been defined in drafts, are these letters/compact forms reserved for the proposed usage? If not, is it likely that these letters/compact forms will be reserved in the future and included in the list above? I did note that both of these drafts state that the compact forms should be added to the list above. Thanks, Kosta _____________________________________________________________ Are you a Techie? Get Your Free Tech Email Address Now! Visit http://www.TechEmail.com _____________________________________________________________ Promote your group and strengthen ties to your members with email@yourgroup.org by Everyone.net http://www.everyone.net/?btn=tag _______________________________________________ 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
- [Sip] Compact forms questions Kosta Koeman
- Re: [Sip] Compact forms questions Robert Sparks
- RE: [Sip] Compact forms questions Tan Ya-Ching ICM N PG U ID A 1