[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sip] Summary (Was: [Re: Question regarding conflicting grammar for IPV6 SIP URI andRFC 3986])
Hadriel Kaplan wrote:
It's ambiguous with path-rootless, no?
I don't think so. I don't think you can generate a token with
"[" and "]" using the path-rootless production rule (unless
they are escaped.)
But anyway I think the AD's should weigh in on what WG should work on
the fix. The fix needs to be applicable to all URIs, and I don't
think we have all the right folks to know what the rfc3986 semantics
really means generally.
Understood; however, I was asked by the chairs to round up
a WG summary on this one. I suspect that once we do so,
the chairs will get the ADs involved to move this along in
the shape they see fit.
Hence, please do eyeball the path-rootless production rule
and make sure my understanding is correct.
Thanks,
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg at {alcatel-lucent.com,bell-labs.com,acm.org}
Web: http://ect.bell-labs.com/who/vkg/
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/lFrom sip-bounces at ietf.org Fri Dec 19 13:12:23 2008
Return-Path: <sip-bounces at ietf.org>
X-Original-To: sip-web-archive at optimus.ietf.org
Delivered-To: ietfarch-sip-web-archive at core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 38DB43A6993;
Fri, 19 Dec 2008 13:12:23 -0800 (PST)
X-Original-To: sip at core3.amsl.com
Delivered-To: sip at core3.amsl.com
Received: from localhost (localhost [127.0.0.1])
by core3.amsl.com (Postfix) with ESMTP id 3FB6B3A6993
for <sip at core3.amsl.com>; Fri, 19 Dec 2008 13:12:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.533
X-Spam-Level:
X-Spam-Status: No, score=-2.533 tagged_above=-999 required=5 tests=[AWL=0.066,
BAYES_00=-2.599]
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 TbNt21UGlImz for <sip at core3.amsl.com>;
Fri, 19 Dec 2008 13:12:21 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39])
by core3.amsl.com (Postfix) with ESMTP id 330563A68DD
for <sip at ietf.org>; Fri, 19 Dec 2008 13:12:21 -0800 (PST)
Received: from umail.lucent.com (h135-3-40-61.lucent.com [135.3.40.61])
by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id mBJLBeTm022580
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Fri, 19 Dec 2008 15:11:41 -0600 (CST)
Received: from [135.185.236.17] (il0015vkg1.ih.lucent.com [135.185.236.17])
by umail.lucent.com (8.13.8/TPES) with ESMTP id mBJLBeDG006845;
Fri, 19 Dec 2008 15:11:40 -0600 (CST)
Message-ID: <494C0E0C.3030907 at alcatel-lucent.com>
Date: Fri, 19 Dec 2008 15:11:40 -0600
From: "Vijay K. Gurbani" <vkg at alcatel-lucent.com>
Organization: Bell Labs Security Technology Research Group
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Hadriel Kaplan <HKaplan at acmepacket.com>
References: <BBE61D1553D8A34F812FF87377B2935F062D9AE8 at ATL1VEXC020.usdom003.tco.tc> <494BF9F7.7010300 at alcatel-lucent.com>
<494BFC47.2030606 at cisco.com>
<E6C2E8958BA59A4FB960963D475F7AC3138E1638DF at mail>
In-Reply-To: <E6C2E8958BA59A4FB960963D475F7AC3138E1638DF at mail>
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
Cc: IETF SIP List <sip at ietf.org>, 'Cullen Jennings' <fluffy at cisco.com>,
"jon.peterson at neustar.biz" <jon.peterson at neustar.biz>
Subject: Re: [Sip] Summary (Was: [Re: Question regarding conflicting grammar
for IPV6 SIP URI andRFC 3986])
X-BeenThere: sip at ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>,
<mailto:sip-request at ietf.org?subject=unsubscribe>
List-Post: <mailto:sip at ietf.org>
List-Help: <mailto:sip-request at ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>,
<mailto:sip-request at ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: sip-bounces at ietf.org
Errors-To: sip-bounces at ietf.org
Hadriel Kaplan wrote:
It's ambiguous with path-rootless, no?
I don't think so. I don't think you can generate a token with
"[" and "]" using the path-rootless production rule (unless
they are escaped.)
But anyway I think the AD's should weigh in on what WG should work on
the fix. The fix needs to be applicable to all URIs, and I don't
think we have all the right folks to know what the rfc3986 semantics
really means generally.
Understood; however, I was asked by the chairs to round up
a WG summary on this one. I suspect that once we do so,
the chairs will get the ADs involved to move this along in
the shape they see fit.
Hence, please do eyeball the path-rootless production rule
and make sure my understanding is correct.
Thanks,
- vijay
--
Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
Email: vkg at {alcatel-lucent.com,bell-labs.com,acm.org}
Web: http://ect.bell-labs.com/who/vkg/
_______________________________________________
Sip mailing list https://www.ietf.org/mistinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip
ailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip