RE: Last Call: draft-ietf-webdav-rfc2518bis (HTTP Extensions forDistributed Authoring - WebDAV) to Proposed Standard

Ted Hardie <hardie@qualcomm.com> Wed, 21 February 2007 04:45 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HJjLi-0006qK-RY; Tue, 20 Feb 2007 23:45:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HJjLh-0006qA-Cq for ietf@ietf.org; Tue, 20 Feb 2007 23:45:01 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJjLc-0003gk-W0 for ietf@ietf.org; Tue, 20 Feb 2007 23:45:01 -0500
Received: from hamtaro.qualcomm.com (hamtaro.qualcomm.com [129.46.61.157]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id l1L4itb1024987 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 20 Feb 2007 20:44:56 -0800
Received: from [67.174.199.226] (vpn-10-50-16-221.qualcomm.com [10.50.16.221]) by hamtaro.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id l1L4isxo023179; Tue, 20 Feb 2007 20:44:55 -0800 (PST)
Mime-Version: 1.0
Message-Id: <p06240602c2017dd7a4c4@[67.174.199.226]>
In-Reply-To: <007e01c75560$7e2d2e20$0202fea9@LROSENTOSHIBA>
References: <E1H2Xk1-00027W-7y@stiedprstage1.ietf.org> <45B4B2E6.80808@gmx.de> <2B148D0B-2A08-4510-9381-1477B858CC9E@cisco.com> <007e01c75560$7e2d2e20$0202fea9@LROSENTOSHIBA>
Date: Tue, 20 Feb 2007 20:44:53 -0800
To: lrosen@rosenlaw.com, ietf@ietf.org
From: Ted Hardie <hardie@qualcomm.com>
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Cc:
Subject: RE: Last Call: draft-ietf-webdav-rfc2518bis (HTTP Extensions forDistributed Authoring - WebDAV) to Proposed Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

At 6:32 PM -0800 2/20/07, Lawrence Rosen wrote:
>Without forcing me to read all the referenced documents, is there an easy
>way to determine whether any IPR disclosures relating to these documents
>need to be correlated and disclosed?
>
>/Larry Rosen
>

Is the IPR search page, linked off of the IETF web page not working for you?
You can search there for draft names or RFC numbers.   If  you are asking
whether it is designed to recursively search all the dependencies in a document
as well, the answer is no.  We do expect people to read our documents.  If
you'd like to suggest it to the tools team as a convenience for those who do
not, I'm sure they'll consider it.  tools-discuss@ietf.org is the right venue
for that suggestion.
		regards,

				Ted Hardie




> > -----Original Message-----
>> From: Cullen Jennings [mailto:fluffy@cisco.com]
>> Sent: Tuesday, February 20, 2007 5:35 PM
>> To: Julian Reschke
>> Cc: ietf@ietf.org
>> Subject: Re: Last Call: draft-ietf-webdav-rfc2518bis (HTTP Extensions
>> forDistributed Authoring - WebDAV) to Proposed Standard
>>
>>
>> On Jan 22, 2007, at 4:49 AM, Julian Reschke wrote:
>>
>> > Hi,
>> >
>> > RFC2518bis updates parts of RFC3253 (DAV:error below DAV:response)
>> > in an
>> > incompatible way, and thus should note it in the front matter
>> > ("Updates: 3253") and mention it as a change near the Changes
>> > Appendix.
>> >
>> > (see <http://ietf.osafoundation.org:8080/bugzilla/show_bug.cgi?
>> > id=258>)
>> >
>> > Best regards, Julian
>>
>>
>> Sent with my behave chair hat on ...
>>
>> This is always a complicated problem of does an update document
>> update the documents that depend on the drafts it's updates. An
>> extreme example is should TLS 1.2 update every document that uses TLS
>> 1.0. It's pretty unwieldy to take that path so I I think a better
>> path is that 3253 depends on 2518 and when we update 3253, then it
>> will be changed to depend on the RFC that comes out of the 2518bis
>> draft.
>>
>> The WG definitely considered the impact of the incompatibilities here
>> and decided that this was an acceptable path - the only question we
>> are trying to sort out here is if the id tracker shows this an up
>> update on 3253 or not.
>>
>> Cullen
>>
>>
>>
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ietf
>
>
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www1.ietf.org/mailman/listinfo/ietf


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf