IETF Logo Mail Archive

Re: [dispatch] RFC 3680 extensibility

"WORLEY, Dale R (Dale)" <dworley@avaya.com> Fri, 11 June 2010 16:09 UTC

Return-Path: <dworley@avaya.com>
X-Original-To: dispatch@core3.amsl.com
Delivered-To: dispatch@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 95AEA28C0E8 for <dispatch@core3.amsl.com>; Fri, 11 Jun 2010 09:09:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level:
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74]
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 3r1DrwvGD+B9 for <dispatch@core3.amsl.com>; Fri, 11 Jun 2010 09:09:10 -0700 (PDT)
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 7ABB728C0E1 for <dispatch@ietf.org>; Fri, 11 Jun 2010 09:09:10 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,404,1272859200"; d="scan'208";a="20180904"
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; 11 Jun 2010 12:09:03 -0400
X-IronPort-AV: E=Sophos;i="4.53,404,1272859200"; d="scan'208";a="471673527"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 11 Jun 2010 12:08:33 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.188]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Fri, 11 Jun 2010 12:08:33 -0400
From: "WORLEY, Dale R (Dale)" <dworley@avaya.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, DISPATCH list <dispatch@ietf.org>
Date: Fri, 11 Jun 2010 12:06:29 -0400
Thread-Topic: RFC 3680 extensibility
Thread-Index: AcsJVbEf5CP1frgBQTGyiKiXjhpJ0wAKlxzh
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B21FD736182@DC-US1MBEX4.global.avaya.com>
References: <FF84A09F50A6DC48ACB6714F4666CC7465C6398042@ESESSCMS0354.eemea.ericsson.se>
In-Reply-To: <FF84A09F50A6DC48ACB6714F4666CC7465C6398042@ESESSCMS0354.eemea.ericsson.se>
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: [dispatch] RFC 3680 extensibility
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jun 2010 16:09:11 -0000

________________________________________
From: dispatch-bounces@ietf.org [dispatch-bounces@ietf.org] On Behalf Of Christer Holmberg [christer.holmberg@ericsson.com]

Section 5.1 of RFC 3680 (reg event package) says:

"Other elements from different namespaces MAY be present for the
purposes of extensibility; elements or attributes from unknown
namespaces MUST be ignored."

However, there is no policy regarding whether the definition of these "other namespaces" needs to be done in IETF - only that they must be ignored if not supported.

3GPP has been discussing a couple of IMS specific cases, in which such extension elements/attributes could be used as solution (no decissions have been made yet), so the question is whether it would require IETF work.
________________________________________

The rule that unknown elements/attributes must be ignored covers you there, doesn't it?  If a non-3GPP system subscribes to an "extended" event package, it will ignore the extensions.

Dale

v2.23.0 | Report a Bug | By Email