Re: [sipcore] draft-barnes-sipcore-rfc4244bis

Hadriel Kaplan <HKaplan@acmepacket.com> Sat, 11 July 2009 19:01 UTC

Return-Path: <HKaplan@acmepacket.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 746173A687A for <sipcore@core3.amsl.com>; Sat, 11 Jul 2009 12:01:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.516
X-Spam-Level:
X-Spam-Status: No, score=-2.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599]
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 jFvV+bFlvW6p for <sipcore@core3.amsl.com>; Sat, 11 Jul 2009 12:01:01 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by core3.amsl.com (Postfix) with ESMTP id 95DDB3A6BDD for <sipcore@ietf.org>; Sat, 11 Jul 2009 12:01:01 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.1.375.2; Sat, 11 Jul 2009 15:01:30 -0400
Received: from mail.acmepacket.com ([127.0.0.1]) by mail ([127.0.0.1]) with mapi; Sat, 11 Jul 2009 15:01:30 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Paul Kyzivat <pkyzivat@cisco.com>, Francois Audet <audet@nortel.com>
Date: Sat, 11 Jul 2009 15:01:14 -0400
Thread-Topic: [sipcore] draft-barnes-sipcore-rfc4244bis
Thread-Index: AcoA5RrQh8/9lHnmSmmRlRIIwLOllgBdIFwg
Message-ID: <E6C2E8958BA59A4FB960963D475F7AC3196190A710@mail>
References: <1246556981.10099.65.camel@victoria-pingtel-com.us.nortel.com> <4A4CFEF1.1000006@cisco.com> <1ECE0EB50388174790F9694F77522CCF1EE8ABC1@zrc2hxm0.corp.nortel.com> <4A566FAE.4030901@cisco.com>
In-Reply-To: <4A566FAE.4030901@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: SIPCORE <sipcore@ietf.org>, Dale Worley <dworley@nortel.com>
Subject: Re: [sipcore] draft-barnes-sipcore-rfc4244bis
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Jul 2009 19:01:02 -0000

> -----Original Message-----
> From: sipcore-bounces@ietf.org [mailto:sipcore-bounces@ietf.org] On Behalf
> Of Paul Kyzivat
> Sent: Thursday, July 09, 2009 6:31 PM
>
> > What we are trying to achieve with the ABNF is:
> >
> > - No ordering requirement
> > - There MUST be exactly ONE hi-index
> > - There MUST be 0 or 1 hi-target parameter
> > - There MUST be 0 or 1 hi-aor parameter
> > - There MAY be any number of hi-extension
> 
> Its already a restriction that parameters (in general) may appear only
> once. It gets asked about from time to time. I forget where it says that.

RFC 3261, section 7.3.1 on Header Field Format, Page 32:

   Even though an arbitrary number of parameter pairs may be attached to
   a header field value, any given parameter-name MUST NOT appear more
   than once.


-hadriel