IETF Logo Mail Archive

[Dime] Regarding 'P' bit setting in Diameter Header

Arud Selvan Sundaramurthy <arud.selvan.sundaramurthy@ericsson.com> Thu, 02 August 2012 07:08 UTC

Return-Path: <arud.selvan.sundaramurthy@ericsson.com>
X-Original-To: dime@ietfa.amsl.com
Delivered-To: dime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6713311E8186 for <dime@ietfa.amsl.com>; Thu, 2 Aug 2012 00:08:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.248
X-Spam-Level:
X-Spam-Status: No, score=-6.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XejI7mw+kXSZ for <dime@ietfa.amsl.com>; Thu, 2 Aug 2012 00:08:23 -0700 (PDT)
Received: from mailgw7.ericsson.se (mailgw7.ericsson.se [193.180.251.48]) by ietfa.amsl.com (Postfix) with ESMTP id E33FE11E8152 for <dime@ietf.org>; Thu, 2 Aug 2012 00:08:22 -0700 (PDT)
X-AuditID: c1b4fb30-b7fd46d000003161-f6-501a2764c787
Received: from esessmw0256.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw7.ericsson.se (Symantec Mail Security) with SMTP id 1B.25.12641.4672A105; Thu, 2 Aug 2012 09:08:21 +0200 (CEST)
Received: from ESESSCMS0357.eemea.ericsson.se ([169.254.1.39]) by esessmw0256.eemea.ericsson.se ([153.88.115.96]) with mapi; Thu, 2 Aug 2012 09:08:21 +0200
From: Arud Selvan Sundaramurthy <arud.selvan.sundaramurthy@ericsson.com>
To: "dime@ietf.org" <dime@ietf.org>
Date: Thu, 02 Aug 2012 09:08:20 +0200
Thread-Topic: Regarding 'P' bit setting in Diameter Header
Thread-Index: Ac1wd9EgGC6l9z6HRAi+axQWKXdYXQ==
Message-ID: <044FE89B8513A3408E08F57DCD25EB1737B397E796@ESESSCMS0357.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_044FE89B8513A3408E08F57DCD25EB1737B397E796ESESSCMS0357e_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrALMWRmVeSWpSXmKPExsUyM+JvrW6qulSAQdMERou5vSvYHBg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVsWLSS/aCi3oVU7+/Ym9gbNXsYuTgkBAwkdiyt6qLkRPIFJO4 cG89WxcjF4eQwClGiQdbvrBCOPMZJRra7jOBVLEJeEhM7HzKBtIsIqAscfqXA4jJIqAicegZ D0iFsICpxOqNP8CqRQSsJKbPvsoIYetJLF5xgB3E5hUIl9gyZxoziM0ItPf7qTVg9cwC4hK3 nsxngrhHQGLJnvPMELaoxMvH/1gh6kUl7rSvZ4Soz5e41nqWFWKmoMTJmU9YJjAKzUIyahaS sllIyiDiOhILdn9ig7C1JZYtfM0MY5858JgJWXwBI/sqRuHcxMyc9HJzvdSizOTi4vw8veLU TYzAWDi45bfBDsZN98UOMUpzsCiJ8+qp7vcXEkhPLEnNTk0tSC2KLyrNSS0+xMjEwSnVwMhf fE9APcNOz3FFuDZv0TXhmF/pel3HY7grM8/0vgt52XPBOS/e+DVHwv9K/TvBqcJ/YgMbtO4o bT3J/vCEp7rx4W25Wcdr1fjefc58FXS6d//yX++nm4VqCfW5ci3tMtx8JPDvc7F+e8evy1Yr Pt53sOzHQSYW3ZvfJ3DuEZOJ4/7/ROPQcSWW4oxEQy3mouJEANFSNbJTAgAA
Subject: [Dime] Regarding 'P' bit setting in Diameter Header
X-BeenThere: dime@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Diameter Maintanence and Extentions Working Group <dime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 02 Aug 2012 07:08:24 -0000

Hi,
I  have a doubt in diameter proxy behaviour when routing  a request.

When diameter proxy receives a request with 'P' bit **NOT SET ** in header   , and having valid routing entry to route the request to next hop, will it route the request to next hop by setting the 'P' bit or will it reply will "DIAMETER_UNABLE_TO_DELIVER" as the 'P' bit is not set.  Will the proxy is allowed to modify the header in this case?


As per bis draft-ietf-dime-rfc3588bis-34.txt in section 6.1.9 , it states

"Relay and proxy agents are not required to perform full inspection of

   incoming messages.  At a minimum, validation of the message header

   and relevant routing AVPs has to be done when relaying messages.".

Does the "minimum header validation" includes checking the 'P' in header by Proxy agent also?
Kindly provide your suggestion on this.

Thanks,
Arud selvan.S.

v2.23.0 | Report a Bug | By Email