Re: [Iptel] idnits draft-ietf-iptel-tel-enumdi-01

Cullen Jennings <fluffy@cisco.com> Sat, 29 October 2005 16:33 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVteD-000529-Tj; Sat, 29 Oct 2005 12:33:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVteB-0004xz-KV for iptel@megatron.ietf.org; Sat, 29 Oct 2005 12:33:36 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09645 for <iptel@ietf.org>; Sat, 29 Oct 2005 12:33:18 -0400 (EDT)
Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVtrz-0007xM-Pf for iptel@ietf.org; Sat, 29 Oct 2005 12:47:52 -0400
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-5.cisco.com with ESMTP; 29 Oct 2005 09:33:26 -0700
X-IronPort-AV: i="3.97,266,1125903600"; d="scan'208"; a="225274409:sNHT698220396"
Received: from vtg-um-e2k4.sj21ad.cisco.com (vtg-um-e2k4.cisco.com [171.70.93.57]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id j9TGXKUw025093; Sat, 29 Oct 2005 09:33:21 -0700 (PDT)
Received: from 10.82.209.156 ([10.82.209.156]) by vtg-um-e2k4.sj21ad.cisco.com ([171.70.93.57]) with Microsoft Exchange Server HTTP-DAV ; Sat, 29 Oct 2005 16:33:52 +0000
User-Agent: Microsoft-Entourage/11.2.1.051004
Date: Sat, 29 Oct 2005 09:33:18 -0700
Subject: Re: [Iptel] idnits draft-ietf-iptel-tel-enumdi-01
From: Cullen Jennings <fluffy@cisco.com>
To: lconroy <lconroy@insensate.co.uk>
Message-ID: <BF88F25E.5D35B%fluffy@cisco.com>
Thread-Topic: [Iptel] idnits draft-ietf-iptel-tel-enumdi-01
Thread-Index: AcXcpnemthxWokiZEdqp2AARJEEJ/A==
In-Reply-To: <6E812970-9C29-443B-9B20-85767B814FF9@insensate.co.uk>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87
Content-Transfer-Encoding: 7bit
Cc: "iptel@ietf.org" <iptel@ietf.org>, Stastny Richard <Richard.Stastny@oefeg.at>
X-BeenThere: iptel@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP Telephony <iptel.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/iptel>, <mailto:iptel-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/iptel>
List-Post: <mailto:iptel@ietf.org>
List-Help: <mailto:iptel-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/iptel>, <mailto:iptel-request@ietf.org?subject=subscribe>
Sender: iptel-bounces@ietf.org
Errors-To: iptel-bounces@ietf.org

Ok, I'm pretty sure I have tracked down what happened to this. The IPR
statement is wrong and it was rejected. It looks like it has the 3667 IPR
boiler plate and it needs the 3978. Anything submitted after last May
without the 3978 has been rejected.

Check you xml has ipr="full3978". Run idnits. XML2RFC will generate many
things that contain all kinds of problems including lines too wide, invalid
characters, and bad IPR.

>From a review point of view, it looks like there is no difference from the
01 version to the 02 version that got mailed to the list. Is that correct?




On 10/28/05 3:03 AM, "lconroy" <lconroy@insensate.co.uk> wrote:

> Hi Cullen, folks,
>   Sorry about that chaps. Eye off the ball here. Repeat after me -
> "Do not Assume".
> I just checked by mail server logs, and it seems to have fallen into
> a black hole in transit - there's no report of rejection at my end,
> but I didn't receive the auto-confirm, so something strange must have
> happened.
> I will re-send to I-D when we come out of shadow.
> For now, Richard has sent a copy to the list. For filling up your
> mailboxes, my apologies.
> 
> Re. id-nits: this is generated from XML using the latest version (at
> the point of generation) of XML2RFC, so it won't have nits.
> 
> all the best,
>    Lawrence
> 
> On 27 Oct 2005, at 19:28, Jennings, Cullen wrote:
> 
>> 
>> I was looking at 01 - I wonder what happened to the 02. Could you
>> please post a copy of the 02 somewhere and mail a link to the list
>> or send me a copy and I can post it somewhere. Or just send a copy
>> to the list.
>> 
>> 
>> -----Original Message-----
>> From: Stastny Richard [mailto:Richard.Stastny@oefeg.at]
>> Sent: Thu 10/27/2005 10:21 AM
>> To: Jennings, Cullen; iptel@ietf.org; lconroy@insensate.co.uk
>> Subject: Re: [Iptel] idnits draft-ietf-iptel-tel-enumdi-01
>> 
>> Now this is very curious
>> 
>> are you talking about -01 or -02?
>> 
>> Lawrence sent in a draft -02 on 14.9 which never showed up
>> (as I saw now)
>> as far as I know Lawrence is normally checking the idnits before
>> 
>> Richard
>> 
>> 
>> ________________________________
>> 
>> Von: iptel-bounces@ietf.org im Auftrag von Cullen Jennings
>> Gesendet: Do 27.10.2005 18:40
>> An: iptel@ietf.org
>> Betreff: [Iptel] idnits draft-ietf-iptel-tel-enumdi-01
>> 
>> 
>> 
>> 
>> idnits 1.73 (17 Jun 2005)
>> 
>> draft-ietf-iptel-tel-enumdi-01.txt:
>> 
>> 
>>   Checking nits according to http://www.ietf.org/ID-Checklist.html:
>>     Checking conformance with RFC 3978/3979 boilerplate...
>>   * The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure
>>     Acknowledgement.
>>     (The document uses RFC 3667 boilerplate or RFC 3978-like
>>     boilerplate instead of verbatim RFC 3978 boilerplate.  After 6
>> May 2005,
>>     submission of drafts without verbatim RFC 3978 boilerplate is not
>>     accepted.)
>> 
>> 
>> _______________________________________________
>> Iptel mailing list
>> Iptel@ietf.org
>> https://www1.ietf.org/mailman/listinfo/iptel
>> 
>> 
>> 
>> _______________________________________________
>> Iptel mailing list
>> Iptel@ietf.org
>> https://www1.ietf.org/mailman/listinfo/iptel
>> 

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