RE: [Sip] comments on draft-hilt-sip-correction-503-01

"Brett Tate" <brett@broadsoft.com> Mon, 03 December 2007 21:04 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzITF-0003W7-GO; Mon, 03 Dec 2007 16:04:53 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1IzITD-0003Vr-Pp for sip-confirm+ok@megatron.ietf.org; Mon, 03 Dec 2007 16:04:51 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzITD-0003Vd-FU for sip@ietf.org; Mon, 03 Dec 2007 16:04:51 -0500
Received: from out003.iad.hostedmail.net ([209.225.56.66]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IzITD-00073b-7I for sip@ietf.org; Mon, 03 Dec 2007 16:04:51 -0500
Received: from ATL1VEXC020.usdom003.tco.tc ([10.158.7.31]) by out003.iad.hostedmail.net with Microsoft SMTPSVC(6.0.3790.3959); Mon, 3 Dec 2007 16:04:50 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sip] comments on draft-hilt-sip-correction-503-01
Date: Mon, 03 Dec 2007 16:04:50 -0500
Message-ID: <BBE61D1553D8A34F812FF87377B2935F01EE0DBB@ATL1VEXC020.usdom003.tco.tc>
In-Reply-To: <47538A57.4010907@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] comments on draft-hilt-sip-correction-503-01
Thread-Index: Acg1gv35/y3WJve3RQGkivbZ4mJsDgAY+HGA
From: Brett Tate <brett@broadsoft.com>
To: Jonathan Rosenberg <jdrosen@cisco.com>, IETF SIP List <sip@ietf.org>
X-OriginalArrivalTime: 03 Dec 2007 21:04:50.0311 (UTC) FILETIME=[24A27970:01C835F0]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc:
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

> I'm really unsure about whether this is an 
> essential correction or not. Its not a 
> functional bug, but a performance bug.

I'm also uncertain if this should be an essential correction.

The only 503 essential corrections that I see needed are clarification
of "server" within the rfc3261 section 21.5.4 and security implications
of honoring a 503's Retry-After.  Draft-hilt-sip-correction-503-01
attempts to provide some clarification concerning "server".  However I
did not notice what should occur if immediate destination IP address of
request was different than source address of 503 response.  Leaving it
vague is ok with me; however the topic (and 503 with Retry-After in
general) should be likely be discussed from a security perspective.

The rest of the draft appears to mainly be an rfc3261 extension and
related justification.


_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip