Re: [sipcore] Extensions to the reg event package

"Worley, Dale R (Dale)" <dworley@avaya.com> Fri, 17 December 2010 17:04 UTC

Return-Path: <dworley@avaya.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 D431D3A692C for <sipcore@core3.amsl.com>; Fri, 17 Dec 2010 09:04:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.498
X-Spam-Level:
X-Spam-Status: No, score=-102.498 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 i94IFHJb-ddA for <sipcore@core3.amsl.com>; Fri, 17 Dec 2010 09:04:09 -0800 (PST)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (nj300815-nj-outbound.net.avaya.com [135.11.29.16]) by core3.amsl.com (Postfix) with ESMTP id D76D33A690B for <sipcore@ietf.org>; Fri, 17 Dec 2010 09:04:08 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAIQnC02HCzI1/2dsb2JhbACkMXOpDQKZIoVKBIRliUw
X-IronPort-AV: E=Sophos;i="4.59,362,1288584000"; d="scan'208";a="50568070"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 17 Dec 2010 12:04:47 -0500
X-IronPort-AV: E=Sophos;i="4.59,362,1288584000"; d="scan'208";a="558895352"
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 17 Dec 2010 12:04:11 -0500
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.90]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Fri, 17 Dec 2010 12:04:10 -0500
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: "Thomson, Martin" <Martin.Thomson@andrew.com>, Paul Kyzivat <pkyzivat@cisco.com>, "sipcore@ietf.org" <sipcore@ietf.org>
Date: Fri, 17 Dec 2010 12:01:00 -0500
Thread-Topic: [sipcore] Extensions to the reg event package
Thread-Index: ActxSNxgv9N7FJTlQcWWShNQZ2FghQAJW4oQCydsFBY=
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B2202288B0E@DC-US1MBEX4.global.avaya.com>
References: <CD5674C3CD99574EBA7432465FC13C1B220228896A@DC-US1MBEX4.global.avaya.com> <4CC07E0F.4030508@cisco.com>, <8B0A9FCBB9832F43971E38010638454F03F31EABA6@SISPE7MB1.commscope.com>
In-Reply-To: <8B0A9FCBB9832F43971E38010638454F03F31EABA6@SISPE7MB1.commscope.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
Subject: Re: [sipcore] Extensions to the reg event package
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: Fri, 17 Dec 2010 17:04:09 -0000

> From: Thomson, Martin [Martin.Thomson@andrew.com]
> 
> In practice, a processor that uses the original schema definitions is
> likely to reject a document that uses the modified structure.
> 
> For instance, the original might define (A, B, *) where * is an
> extension point, and the extension defines (A, B, C, *).  Because if
> the way that * is defined, it means anything not in this namespace.
> If the original sees C, which claims to be in the same namespace, it
> rejects it.

Then, to phrase it another way, schemas are extensible in that
elements of other namespaces may be inserted, but not new elements of
the existing namespace.

> The size of namespace declarations is a common source of complaints.
> The usual response is to point folks at ASN.1+?ER.  I wouldn't dream
> of being so rude.

The DER and PER encodings do seem to be much denser, but I don't see
any mechanism for extensibility.  XER seems to be essentially what
we're already doing.

Dale