IETF Logo Mail Archive

[Dime] RFC 3588 - fixed positioned session-ID AVPs

"David Lehmann" <dlehmann@ulticom.com> Tue, 31 August 2010 13:12 UTC

Return-Path: <dlehmann@ulticom.com>
X-Original-To: dime@core3.amsl.com
Delivered-To: dime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 619633A6835 for <dime@core3.amsl.com>; Tue, 31 Aug 2010 06:12:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.414
X-Spam-Level:
X-Spam-Status: No, score=-2.414 tagged_above=-999 required=5 tests=[AWL=0.184, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 YUvaJa8RJs5H for <dime@core3.amsl.com>; Tue, 31 Aug 2010 06:12:45 -0700 (PDT)
Received: from bw.ulticom.com (bw.ulticom.com [208.255.120.43]) by core3.amsl.com (Postfix) with ESMTP id 2FEAD3A690E for <dime@ietf.org>; Tue, 31 Aug 2010 06:12:45 -0700 (PDT)
Received: from colby.ulticom.com (colby.ulticom.com [192.73.206.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by bw.ulticom.com (BorderWare Security Platform) with ESMTP id 8D47835CC1C0E5CB for <dime@ietf.org>; Tue, 31 Aug 2010 09:13:15 -0400 (EDT)
Received: from MTLEXVS01.ulticom.com (mtlex01.ulticom.com [172.16.40.5]) by colby.ulticom.com (8.13.4/8.12.10) with ESMTP id o7VDDA6Q001563 for <dime@ietf.org>; Tue, 31 Aug 2010 09:13:14 -0400 (EDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB490E.4296D6CE"
Date: Tue, 31 Aug 2010 09:13:10 -0400
Message-ID: <A51D8ACD861B7E41BFC7FE5C64BE96481167B0F1@MTLEXVS01.ulticom.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: RFC 3588 - fixed positioned session-ID AVPs
Thread-Index: ActJDhHpu5bXx/dWT/OYD3e13pPP3Q==
From: David Lehmann <dlehmann@ulticom.com>
To: dime@ietf.org
Received-SPF: none
Subject: [Dime] RFC 3588 - fixed positioned session-ID AVPs
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dime>
List-Post: <mailto:dime@ietf.org>
List-Help: <mailto:dime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dime>, <mailto:dime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Aug 2010 13:12:49 -0000

Hello,
 
In RFC 3588 (and 3588bis), messages with session IDs are defined with
the session ID AVPs with a fixed position which is immediately following
the header. (e.g. section 8.3.1)  However, this is in contradiction with
section 8.8 which states, "When present, the Session-Id SHOULD appear
immediately following the Diameter Header (see Section 3)."
 
By using "SHOULD", the spec is stating that the session-ID AVP could be
in any position in the message.

 

--

David Lehmann

Ulticom, Inc.

856-787-2952

v2.23.0 | Report a Bug | By Email