From fred@cisco.com Fri Jun 4 13:00:26 2010 Return-Path: X-Original-To: tools-discuss@core3.amsl.com Delivered-To: tools-discuss@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B280B3A6890 for ; Fri, 4 Jun 2010 13:00:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -108.318 X-Spam-Level: X-Spam-Status: No, score=-108.318 tagged_above=-999 required=5 tests=[AWL=-0.319, BAYES_50=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] 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 jBDLLc2vwWUW for ; Fri, 4 Jun 2010 13:00:25 -0700 (PDT) Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id 868233A6359 for ; Fri, 4 Jun 2010 13:00:25 -0700 (PDT) Authentication-Results: sj-iport-3.cisco.com; dkim=neutral (message not signed) header.i=none X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAOP3CEyrR7Hu/2dsb2JhbACeRHGlOJl+hRcEg0k X-IronPort-AV: E=Sophos;i="4.53,362,1272844800"; d="scan'208";a="225403165" Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-3.cisco.com with ESMTP; 04 Jun 2010 20:00:11 +0000 Received: from stealth-10-32-244-221.cisco.com (stealth-10-32-244-221.cisco.com [10.32.244.221]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o54K01HC003526; Fri, 4 Jun 2010 20:00:03 GMT Received: from [127.0.0.1] by stealth-10-32-244-221.cisco.com (PGP Universal service); Fri, 04 Jun 2010 13:00:11 -0700 X-PGP-Universal: processed; by stealth-10-32-244-221.cisco.com on Fri, 04 Jun 2010 13:00:11 -0700 From: Fred Baker Date: Fri, 4 Jun 2010 12:59:55 -0700 Message-Id: <54AFE1A8-8191-4005-ABB0-76AC692F8E99@cisco.com> To: IETF TOOLS discussion Mime-Version: 1.0 (Apple Message framework v1078) X-Mailer: Apple Mail (2.1078) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: draft-ietf-v6ops-cpe-simple-security@tools.ietf.org, draft-ietf-v6ops-ipv6-cpe-router@tools.ietf.org, Ron Bonica Subject: [Tools-discuss] issue with id-nits X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jun 2010 20:00:26 -0000 Houston, we have a problem... The authors of draft-ietf-v6ops-cpe-simple-security and = draft-ietf-v6ops-ipv6-cpe-router checked their drafts against = http://tools.ietf.org/tools/idnits/ and came up with at most a couple of = glitches like=20 > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(351): Unexpected reference = format: '...ent ([RFC4862]/[RFC...' When I do the same, I get something like > idnits 2.12.04=20 >=20 > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt: > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(317): RFC 2119 keyword: = G-2: The IPv6 CE router MUST implement ICMP according to [RFC4443].. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(318): RFC 2119 keyword: = In particular point to point links MUST be handled as described. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(321): RFC 2119 keyword: = G-3: The IPv6 CE router MUST NOT forward any IPv6 traffic between. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(349): RFC 2119 keyword: = W-1: When the router is attached to the WAN interface link it MUST. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(351): Unexpected reference = format: '...ent ([RFC4862]/[RFC...' > --> interface address assignment ([RFC4862]/[RFC3315]). > ^ > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(353): RFC 2119 keyword: = W-2: The IPv6 CE router MUST generate a link-local address and. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(356): RFC 2119 keyword: = source address used in the subsequent Router Solicitation MUST. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(359): RFC 2119 keyword: = W-3: Absent of other routing information the IPv6 CE router MUST use. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(364): RFC 2119 keyword: = W-4: The router MUST act as a requesting router for the purposes of. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(368): RFC 2119 keyword: = (IA_PD) SHOULD be done as a single DHCPv6 session.. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(373): RFC 2119 keyword: = the IPv6 CE router MUST support IPv6 over Ethernet [RFC2464].. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(376): RFC 2119 keyword: = router MUST support IPv6 over PPP [RFC5072].. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(380): RFC 2119 keyword: = logical channel, the NCPs MUST be treated as independent of. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(396): RFC 2119 keyword: = WAA-1: The IPv6 CE router MUST support SLAAC [RFC4862].. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(398): RFC 2119 keyword: = WAA-2: The IPv6 CE router MUST follow the recommendation in. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(403): RFC 2119 keyword: = WAA-3: The IPv6 CE router MUST support DHCPv6 [RFC3315] client. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(406): RFC 2119 keyword: = WAA-4: The IPv6 CE router MUST be able to support the following. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(410): RFC 2119 keyword: = WAA-5: The IPv6 CE router SHOULD support the DHCPv6 SNTP option. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(414): RFC 2119 keyword: = [RFC4861]) with the M-flag set to 1, the IPv6 CE router MUST. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(418): RFC 2119 keyword: = SLAAC it MAY do DHCPv6 address assignment (request an IA_NA). > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(422): RFC 2119 keyword: = address(es) from either SLAAC or DHCPv6, then it MUST create. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(427): RFC 2119 keyword: = WAA-9: As a router the IPv6 CE router MUST follow the weak host. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(435): RFC 2119 keyword: = WPD-1: The IPv6 CE router MUST support DHCPv6 prefix delegation. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(439): RFC 2119 keyword: = WPD-2: The IPv6 CE router MAY indicate as a hint to the delegating. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(440): RFC 2119 keyword: = router the size of the prefix it requires. If so, it MUST. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(442): RFC 2119 keyword: = its interfaces rounded up to the nearest nibble and MUST be. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(452): RFC 2119 keyword: = WPD-3: The IPv6 CE router MUST be prepared to accept a delegated. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(455): RFC 2119 keyword: = interfaces, the IPv6 CE router SHOULD log a system management. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(458): RFC 2119 keyword: = WPD-4: The IPv6 CE router MUST always initiate DHCPv6 prefix. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(463): RFC 2119 keyword: = Router Advertisement it MUST also request an IA_NA option in. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(467): RFC 2119 keyword: = multiple, more-specific routes, the IPv6 CE router MUST. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(475): RFC 2119 keyword: = (a) The IPv6 CE router SHOULD send an ICMPv6 Destination. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(481): RFC 2119 keyword: = DHCPv6, it MUST accept an IA_PD in DHCPv6 Advertise/Reply. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(485): RFC 2119 keyword: = WPD-8: By default an IPv6 CE router MUST NOT initiate any dynamic. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(525): RFC 2119 keyword: = L-1: The IPv6 CE router MUST support ULA addressing [RFC4193].. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(527): RFC 2119 keyword: = L-2: The IPv6 CE router MUST have a ULA prefix that it maintains. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(530): RFC 2119 keyword: = L-3: The value of the ULA prefix SHOULD be user configurable.. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(532): RFC 2119 keyword: = L-4: By default the IPv6 CE router MUST act as a site border router. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(536): RFC 2119 keyword: = L-5: The IPv6 CE router MUST support router behavior according to. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(539): RFC 2119 keyword: = L-6: The IPv6 CE router MUST assign a separate /64 from its. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(543): RFC 2119 keyword: = L-7: The IPv6 CE router MUST make each LAN interface an advertising. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(547): RFC 2119 keyword: = Option's A and L-flags MUST be set to 1 by default.. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(549): RFC 2119 keyword: = L-9: The A and L-flags setting SHOULD be user configurable.. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(551): RFC 2119 keyword: = L-10: The IPv6 CE router MUST support a DHCPv6 server capable of. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(565): RFC 2119 keyword: = IA_NA option, it SHOULD set M=3D0 and O=3D1 in its Router. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(568): RFC 2119 keyword: = L-12: The IPv6 CE router MUST support providing DNS information in. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(571): RFC 2119 keyword: = L-13: The IPv6 CE router SHOULD make available a subset of DHCPv6. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(578): RFC 2119 keyword: = period, then the IPv6 CE router MUST immediately advertise the. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(583): RFC 2119 keyword: = L-15: The IPv6 CE router MUST send an ICMP Destination Unreachable. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(600): RFC 2119 keyword: = S-1: The IPv6 CE router SHOULD support. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(603): RFC 2119 keyword: = S-2: The IPv6 CE router MUST support ingress filtering in accordance. > tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(604): Unexpected reference = format: '...with [RFC2827](BCP ...' > --> with [RFC2827](BCP 38) The file contains the specified reference to RFC 2119, in section 1.1 in = both cases, and we are using the same version of the checker. Help? I'm going to file the report saying that id-nits is wrong, which I = would rather not do.= From ietfdbh@comcast.net Mon Jun 14 13:38:58 2010 Return-Path: X-Original-To: tools-discuss@core3.amsl.com Delivered-To: tools-discuss@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 579F03A68F0 for ; Mon, 14 Jun 2010 13:38:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.147 X-Spam-Level: X-Spam-Status: No, score=-0.147 tagged_above=-999 required=5 tests=[AWL=-0.148, BAYES_50=0.001] 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 rVDr24dSOIGA for ; Mon, 14 Jun 2010 13:38:57 -0700 (PDT) Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [76.96.62.16]) by core3.amsl.com (Postfix) with ESMTP id 23A753A635F for ; Mon, 14 Jun 2010 13:38:57 -0700 (PDT) Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52]) by qmta01.westchester.pa.mail.comcast.net with comcast id VpZP1e00717dt5G51wf1vQ; Mon, 14 Jun 2010 20:39:01 +0000 Received: from 23FX1C1 ([67.189.235.106]) by omta13.westchester.pa.mail.comcast.net with comcast id Vwev1e00N2JQnJT3Zwf12K; Mon, 14 Jun 2010 20:39:01 +0000 From: "David Harringoton" To: Date: Mon, 14 Jun 2010 16:38:54 -0400 Message-ID: <26D3811086D24939BE02F6A5A9057927@23FX1C1> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcsL5dQvf+Tyk17OQa23Ziyml0eizw== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931 Subject: [Tools-discuss] dependencies link X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jun 2010 20:38:58 -0000 Hi, In the datatracker, there is a link to "dependencies on this draft". The link is to Bill's utility, and the utility is not accessible. I would find it very helpful to have such a dependency tool. Can the tools team either get Bill's utility made accessible or develop another dependency tool? thanks, David Harrington Area Director IETF Transport Area From spencer@wonderhamster.org Tue Jun 15 12:19:06 2010 Return-Path: X-Original-To: tools-discuss@core3.amsl.com Delivered-To: tools-discuss@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 60D9D3A69B8 for ; Tue, 15 Jun 2010 12:19:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.002 X-Spam-Level: X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[BAYES_50=0.001, STOX_REPLY_TYPE=0.001] 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 qeT1TTVVdz6O for ; Tue, 15 Jun 2010 12:19:05 -0700 (PDT) Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id 7F67D3A696C for ; Tue, 15 Jun 2010 12:19:05 -0700 (PDT) Received: from S73602b ([220.231.21.146]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0MRoht-1OquAs0D0r-00Ta47; Tue, 15 Jun 2010 15:19:09 -0400 Message-ID: From: "Spencer Dawkins" To: "IETF TOOLS discussion" Date: Wed, 16 Jun 2010 03:18:58 +0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5931 X-Provags-ID: V01U2FsdGVkX19Wp80ZryZwkybKXAnd5JzuPTm/aOt2zjfo70B Zw9oj3R82CYG2RkGbVmRVrGw3+Y0ceUYXVLlP7TVQIjieVx3vl cW2rFXPyWHs06iFGwJe3ThmVeqA3oSPj3FX7jow9rk= Subject: [Tools-discuss] Concluded working groups page seems to be broken X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jun 2010 19:19:06 -0000 Hi, When I click on http://tools.ietf.org/wg/concluded/provreg, it is just showing me the list of all concluded working groups - no detail on provreg itself. It should be showing me things like the charter when the working group was concluded, the RFCs produced, etc. This seems to be true for other concluded working groups as well. Thanks, Spencer From brian@innovationslab.net Tue Jun 15 12:26:13 2010 Return-Path: X-Original-To: tools-discuss@core3.amsl.com Delivered-To: tools-discuss@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A79203A68A7 for ; Tue, 15 Jun 2010 12:26:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.297 X-Spam-Level: X-Spam-Status: No, score=-1.297 tagged_above=-999 required=5 tests=[AWL=-0.187, BAYES_05=-1.11] 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 kjvUd2+SzNYI for ; Tue, 15 Jun 2010 12:26:12 -0700 (PDT) Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) by core3.amsl.com (Postfix) with ESMTP id D35863A6817 for ; Tue, 15 Jun 2010 12:26:12 -0700 (PDT) Received: from clairseach.fuaim.com (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id E163E882F2; Tue, 15 Jun 2010 12:26:16 -0700 (PDT) Received: from clemson.jhuapl.edu (unknown [128.244.207.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id F03421369341; Tue, 15 Jun 2010 12:26:15 -0700 (PDT) Message-ID: <4C17D3D0.2030605@innovationslab.net> Date: Tue, 15 Jun 2010 15:26:08 -0400 From: Brian Haberman User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: Spencer Dawkins References: In-Reply-To: X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: IETF TOOLS discussion Subject: Re: [Tools-discuss] Concluded working groups page seems to be broken X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jun 2010 19:26:13 -0000 Spencer, Seems to work for me using http://tools.ietf.org/wg/provreg/. Brian On 6/15/10 3:18 PM, Spencer Dawkins wrote: > Hi, > > When I click on http://tools.ietf.org/wg/concluded/provreg, it is just > showing me the list of all concluded working groups - no detail on > provreg itself. > > It should be showing me things like the charter when the working group > was concluded, the RFCs produced, etc. > > This seems to be true for other concluded working groups as well. > > Thanks, > > Spencer > _______________________________________________ > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/tools-discuss From spencer@wonderhamster.org Tue Jun 15 16:07:57 2010 Return-Path: X-Original-To: tools-discuss@core3.amsl.com Delivered-To: tools-discuss@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C5EB73A69F1 for ; Tue, 15 Jun 2010 16:07:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.368 X-Spam-Level: X-Spam-Status: No, score=-0.368 tagged_above=-999 required=5 tests=[AWL=0.370, BAYES_20=-0.74, STOX_REPLY_TYPE=0.001] 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 XutHDn86VmMY for ; Tue, 15 Jun 2010 16:07:57 -0700 (PDT) Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) by core3.amsl.com (Postfix) with ESMTP id B02D93A69AA for ; Tue, 15 Jun 2010 16:07:56 -0700 (PDT) Received: from S73602b ([220.231.21.146]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0MfWD5-1OaZyy1lJD-00OzXw; Tue, 15 Jun 2010 19:07:59 -0400 Message-ID: <8C2D6032405045D0AA6E2C9A21EA475C@china.huawei.com> From: "Spencer Dawkins" To: "Brian Haberman" References: <4C17D3D0.2030605@innovationslab.net> Date: Wed, 16 Jun 2010 07:07:46 +0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5931 X-Provags-ID: V01U2FsdGVkX1/M1HvnrtoFljfN8MlVKD2j/cl3X4CPbTlfhR8 Fa2K89F2PwUpwX0MAXk200ekyBbL3urB+XS11gCB9TTsCISdKj tQS8ElxxxugrDnDiPmPy2mfEcMpMYMlnFZnaaqfb2Q= Cc: IETF TOOLS discussion Subject: Re: [Tools-discuss] Concluded working groups page seems to be broken X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jun 2010 23:07:57 -0000 OK, I couldn't be more mystified. > Spencer, > Seems to work for me using http://tools.ietf.org/wg/provreg/. > > Brian But it's working for me now - thanks! Spencer > On 6/15/10 3:18 PM, Spencer Dawkins wrote: >> Hi, >> >> When I click on http://tools.ietf.org/wg/concluded/provreg, it is just >> showing me the list of all concluded working groups - no detail on >> provreg itself. >> >> It should be showing me things like the charter when the working group >> was concluded, the RFCs produced, etc. >> >> This seems to be true for other concluded working groups as well. >> >> Thanks, >> >> Spencer >> _______________________________________________ >> Tools-discuss mailing list >> Tools-discuss@ietf.org >> https://www.ietf.org/mailman/listinfo/tools-discuss > From ietfdbh@comcast.net Wed Jun 16 10:57:51 2010 Return-Path: X-Original-To: tools-discuss@core3.amsl.com Delivered-To: tools-discuss@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CD40E3A6B5B for ; Wed, 16 Jun 2010 10:57:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.163 X-Spam-Level: X-Spam-Status: No, score=-0.163 tagged_above=-999 required=5 tests=[AWL=-0.164, BAYES_50=0.001] 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 Ui54ttGCCg2R for ; Wed, 16 Jun 2010 10:57:50 -0700 (PDT) Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [76.96.59.212]) by core3.amsl.com (Postfix) with ESMTP id C7ABD3A6B14 for ; Wed, 16 Jun 2010 10:57:50 -0700 (PDT) Received: from omta05.westchester.pa.mail.comcast.net ([76.96.62.43]) by qmta14.westchester.pa.mail.comcast.net with comcast id Wacr1e0010vyq2s5EhxwAN; Wed, 16 Jun 2010 17:57:56 +0000 Received: from 23FX1C1 ([67.189.235.106]) by omta05.westchester.pa.mail.comcast.net with comcast id Whxw1e0012JQnJT3Rhxw1e; Wed, 16 Jun 2010 17:57:56 +0000 From: "David Harringoton" To: Date: Wed, 16 Jun 2010 13:57:54 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcsNfXIQyerE5e4HQo+lDtyADLdjRA== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931 Subject: [Tools-discuss] issue tracker? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jun 2010 17:57:51 -0000 Hi, RT used to be available for issue tracking. Is that still available, or an alternative? Where does a WG chair find it, or get access to it? thanks, David Harrington Area director IETF Transport Area From julian.reschke@gmx.de Wed Jun 16 11:04:22 2010 Return-Path: X-Original-To: tools-discuss@core3.amsl.com Delivered-To: tools-discuss@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BEC473A6821 for ; Wed, 16 Jun 2010 11:04:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.781 X-Spam-Level: X-Spam-Status: No, score=-3.781 tagged_above=-999 required=5 tests=[AWL=-2.671, BAYES_05=-1.11] 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 Vndn16QfHX4E for ; Wed, 16 Jun 2010 11:04:22 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 81C013A6B50 for ; Wed, 16 Jun 2010 11:04:21 -0700 (PDT) Received: (qmail invoked by alias); 16 Jun 2010 18:04:20 -0000 Received: from p508FED6A.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.237.106] by mail.gmx.net (mp065) with SMTP; 16 Jun 2010 20:04:20 +0200 X-Authenticated: #1915285 X-Provags-ID: V01U2FsdGVkX1+kWbdgU2ukuacOJzrbPvMo9myLsWLxakqCMeFx0r mj3YmjMIDMgc9H Message-ID: <4C19121B.4040205@gmx.de> Date: Wed, 16 Jun 2010 20:04:11 +0200 From: Julian Reschke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4 MIME-Version: 1.0 To: David Harringoton References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: tools-discuss@ietf.org Subject: Re: [Tools-discuss] issue tracker? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jun 2010 18:04:22 -0000 On 16.06.2010 19:57, David Harringoton wrote: > Hi, > > RT used to be available for issue tracking. > Is that still available, or an alternative? > ... tools.ietf.org offers Subversion and Trac for Working Groups (you may have to ping Henrik L. to get it set up). Best regards, Julian From spencer@wonderhamster.org Wed Jun 16 13:52:11 2010 Return-Path: X-Original-To: tools-discuss@core3.amsl.com Delivered-To: tools-discuss@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9ABF73A6927 for ; Wed, 16 Jun 2010 13:52:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.235 X-Spam-Level: X-Spam-Status: No, score=-0.235 tagged_above=-999 required=5 tests=[AWL=0.505, BAYES_20=-0.74] 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 EYXQHeb80bTe for ; Wed, 16 Jun 2010 13:52:10 -0700 (PDT) Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id 4C48B3A67A2 for ; Wed, 16 Jun 2010 13:52:10 -0700 (PDT) Received: from S73602b ([220.231.21.146]) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis) id 0MDAAO-1OSEhZ43Lw-00GkUF; Wed, 16 Jun 2010 16:52:14 -0400 Message-ID: <1797432E955F4C68B577F089FC57E40B@china.huawei.com> From: "Spencer Dawkins" To: "Julian Reschke" , "David Harringoton" References: <4C19121B.4040205@gmx.de> Date: Thu, 17 Jun 2010 04:51:57 +0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5931 X-Provags-ID: V01U2FsdGVkX18t4GgLnCAvrIO3mbR3Y5Zb+jTLGAiUalZFPjS kuEQIAPXHJhqQ/f/VKPPNgH4pQmZuYDsuCjZrAtgCJ3mSdvhvg XFZiHPWduL+L1adY3MrXqqydlDrLogS43GXcqtYuxA= Cc: tools-discuss@ietf.org Subject: Re: [Tools-discuss] issue tracker? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jun 2010 20:52:11 -0000 (and it works well enough that the IAB is now using it as well) > tools.ietf.org offers Subversion and Trac for Working Groups (you may > have to ping Henrik L. to get it set up). > > Best regards, Julian Spencer From stpeter@stpeter.im Wed Jun 16 14:38:52 2010 Return-Path: X-Original-To: tools-discuss@core3.amsl.com Delivered-To: tools-discuss@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7166628C172 for ; Wed, 16 Jun 2010 14:38:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.359 X-Spam-Level: X-Spam-Status: No, score=-2.359 tagged_above=-999 required=5 tests=[AWL=0.240, 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 kV9VjQfACFgU for ; Wed, 16 Jun 2010 14:38:50 -0700 (PDT) Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 7DCF33A6359 for ; Wed, 16 Jun 2010 14:38:50 -0700 (PDT) Received: from squire.local (dsl-228-47.dynamic-dsl.frii.net [216.17.228.47]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 9271E403F3 for ; Wed, 16 Jun 2010 15:38:54 -0600 (MDT) Message-ID: <4C19446D.2070605@stpeter.im> Date: Wed, 16 Jun 2010 15:38:53 -0600 From: Peter Saint-Andre User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: tools-discuss@ietf.org References: In-Reply-To: X-Enigmail-Version: 1.0.1 OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms020504040609050600030806" Subject: Re: [Tools-discuss] issue tracker? X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jun 2010 21:38:52 -0000 This is a cryptographically signed message in MIME format. --------------ms020504040609050600030806 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 6/16/10 11:57 AM, David Harringoton wrote: > Where does a WG chair find it, or get access to it? Off the relevant wiki page. For example: http://trac.tools.ietf.org/wg/xmpp/trac/report/1 /psa --------------ms020504040609050600030806 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIWnDCC B1cwggY/oAMCAQICAVUwDQYJKoZIhvcNAQEFBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBT aWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRl IENsaWVudCBDQTAeFw0wOTA3MDYwMDAwMDFaFw0xMDA3MDYyMzU5NTlaMIHCMQswCQYDVQQG EwJVUzERMA8GA1UECBMIQ29sb3JhZG8xDzANBgNVBAcTBkRlbnZlcjEiMCAGA1UEChMZWE1Q UCBTdGFuZGFyZHMgRm91bmRhdGlvbjEsMCoGA1UECxMjU3RhcnRDb20gVHJ1c3RlZCBDZXJ0 aWZpY2F0ZSBNZW1iZXIxGjAYBgNVBAMTEVBldGVyIFNhaW50LUFuZHJlMSEwHwYJKoZIhvcN AQkBFhJzdHBldGVyQHN0cGV0ZXIuaW0wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB AQCas7Mrnh02GakN8sft+HJpU4MwBxEgrGDZ2ZzUxDDt2sEhM+9Q74h955MtgMhK3TeBf6Hs hDh/8Z9G//k2qNA0M2S5rejTqrmW0Jabca/L7BUZ0GhnU2N/2zeciFUmuZ4A2l1T5IMX2ZVP XnNIaefBtbImJAbDz3T0vxkzTtcqgW3wL83PMDiqiuM+e1k+VPvOW4f5ZSGkPIhYCDpWqNE5 wZvjrLNMc8jZOPs9DrsYuIVwU72Vhy1tkEh+w6YpYHrdEUAe+eKe6TuxqZ60e9z3O36uiV// Ms274iD6PbA/IGazJgaAdg6tvPehwTYGJAGmv3PsJKkLGjgoh+RrrM1LAgMBAAGjggOKMIID hjAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUH AwQwHQYDVR0OBBYEFOyws3XWgIY9FP1POVqjdZP9Lu38MB0GA1UdEQQWMBSBEnN0cGV0ZXJA c3RwZXRlci5pbTCBqAYDVR0jBIGgMIGdgBR7iZySlyShhEcCy3T8LvSs3DLl86GBgaR/MH0x CzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUg RGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMSkwJwYDVQQDEyBTdGFydENvbSBDZXJ0aWZp Y2F0aW9uIEF1dGhvcml0eYIBDzCCAUcGA1UdIASCAT4wggE6MIIBNgYLKwYBBAGBtTcBAgAw ggElMC4GCCsGAQUFBwIBFiJodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9wb2xpY3kucGRmMDQG CCsGAQUFBwIBFihodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9pbnRlcm1lZGlhdGUucGRmMIG8 BggrBgEFBQcCAjCBrzAUFg1TdGFydENvbSBMdGQuMAMCAQEagZZMaW1pdGVkIExpYWJpbGl0 eSwgcmVhZCB0aGUgc2VjdGlvbiAqTGVnYWwgTGltaXRhdGlvbnMqIG9mIHRoZSBTdGFydENv bSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSBQb2xpY3kgYXZhaWxhYmxlIGF0IGh0dHA6Ly93 d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwYwYDVR0fBFwwWjAroCmgJ4YlaHR0cDovL3d3 dy5zdGFydHNzbC5jb20vY3J0dTMtY3JsLmNybDAroCmgJ4YlaHR0cDovL2NybC5zdGFydHNz bC5jb20vY3J0dTMtY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0 cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczMvY2xpZW50L2NhMEIGCCsGAQUFBzAC hjZodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MzLmNsaWVudC5jYS5j cnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBBQUA A4IBAQBgv4xFXZqDKSOtnPOVbqOh1brj7oxRaVYk7N0MJG7x9Y/wkO3iwRwizVLcC1bA+D/R gyFilXx6IQWE63Ge2tu+Y4w5QoHYwuUFQuBZuxvZpOa3ykdgPlBQaBM8m+Ien0skwNggaizA X9Pc/sMLpP3jkO1iSF4agy4r5Ed+4G10mP5X0zO3gQwq9Uj4F9tX+58kU+fM1P8Sh+BYR4r/ kSbKE3tWcMaKblWPGwX0nYD26Je7Qb+uX/J5lCgozBrHXQWq8N98iklASf2pv+32Oi1dEjmM UgAm/J2+YmxaI02+c+H6QH8+F3RUjCiRg9XqUNjcrNrnTFnm/iMMZADktsXPMIIHVzCCBj+g AwIBAgIBVTANBgkqhkiG9w0BAQUFADCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0 Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcx ODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50 IENBMB4XDTA5MDcwNjAwMDAwMVoXDTEwMDcwNjIzNTk1OVowgcIxCzAJBgNVBAYTAlVTMREw DwYDVQQIEwhDb2xvcmFkbzEPMA0GA1UEBxMGRGVudmVyMSIwIAYDVQQKExlYTVBQIFN0YW5k YXJkcyBGb3VuZGF0aW9uMSwwKgYDVQQLEyNTdGFydENvbSBUcnVzdGVkIENlcnRpZmljYXRl IE1lbWJlcjEaMBgGA1UEAxMRUGV0ZXIgU2FpbnQtQW5kcmUxITAfBgkqhkiG9w0BCQEWEnN0 cGV0ZXJAc3RwZXRlci5pbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAJqzsyue HTYZqQ3yx+34cmlTgzAHESCsYNnZnNTEMO3awSEz71DviH3nky2AyErdN4F/oeyEOH/xn0b/ +Tao0DQzZLmt6NOquZbQlptxr8vsFRnQaGdTY3/bN5yIVSa5ngDaXVPkgxfZlU9ec0hp58G1 siYkBsPPdPS/GTNO1yqBbfAvzc8wOKqK4z57WT5U+85bh/llIaQ8iFgIOlao0TnBm+Oss0xz yNk4+z0Ouxi4hXBTvZWHLW2QSH7Dpilget0RQB754p7pO7GpnrR73Pc7fq6JX/8yzbviIPo9 sD8gZrMmBoB2Dq2896HBNgYkAaa/c+wkqQsaOCiH5GuszUsCAwEAAaOCA4owggOGMAkGA1Ud EwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAdBgNV HQ4EFgQU7LCzddaAhj0U/U85WqN1k/0u7fwwHQYDVR0RBBYwFIESc3RwZXRlckBzdHBldGVy LmltMIGoBgNVHSMEgaAwgZ2AFHuJnJKXJKGERwLLdPwu9KzcMuXzoYGBpH8wfTELMAkGA1UE BhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFs IENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g QXV0aG9yaXR5ggEPMIIBRwYDVR0gBIIBPjCCATowggE2BgsrBgEEAYG1NwECADCCASUwLgYI KwYBBQUHAgEWImh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUH AgEWKGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwgbwGCCsGAQUF BwICMIGvMBQWDVN0YXJ0Q29tIEx0ZC4wAwIBARqBlkxpbWl0ZWQgTGlhYmlsaXR5LCByZWFk IHRoZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRp ZmljYXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFy dHNzbC5jb20vcG9saWN5LnBkZjBjBgNVHR8EXDBaMCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0 c3NsLmNvbS9jcnR1My1jcmwuY3JsMCugKaAnhiVodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9j cnR1My1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsGAQUFBzABhi1odHRwOi8vb2Nz cC5zdGFydHNzbC5jb20vc3ViL2NsYXNzMy9jbGllbnQvY2EwQgYIKwYBBQUHMAKGNmh0dHA6 Ly93d3cuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczMuY2xpZW50LmNhLmNydDAjBgNV HRIEHDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQEFBQADggEBAGC/ jEVdmoMpI62c85Vuo6HVuuPujFFpViTs3QwkbvH1j/CQ7eLBHCLNUtwLVsD4P9GDIWKVfHoh BYTrcZ7a275jjDlCgdjC5QVC4Fm7G9mk5rfKR2A+UFBoEzyb4h6fSyTA2CBqLMBf09z+wwuk /eOQ7WJIXhqDLivkR37gbXSY/lfTM7eBDCr1SPgX21f7nyRT58zU/xKH4FhHiv+RJsoTe1Zw xopuVY8bBfSdgPbol7tBv65f8nmUKCjMGsddBarw33yKSUBJ/am/7fY6LV0SOYxSACb8nb5i bFojTb5z4fpAfz4XdFSMKJGD1epQ2Nys2udMWeb+IwxkAOS2xc8wggfiMIIFyqADAgECAgEP MA0GCSqGSIb3DQEBBQUAMH0xCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQu MSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMSkwJwYDVQQD EyBTdGFydENvbSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw0wNzEwMjQyMTAzMzJaFw0x MjEwMjIyMTAzMzJaMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEr MCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMv U3RhcnRDb20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwggEiMA0G CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC5o0luEj4gypQIp71Xi2TlXyLYrj9WkRy+d9BO 0FHPYnAsC99/jx/ibNRwIfAoFhZd+LDscdRSckvwuFSz0bKg3z+9o7cwlVAC9AwMWe8IM0Lx c+8etYxsX4WIamG9fjzzi5GAW5ESKzzIN3SxHSplyGCWFwx/pgf1f4y6O9/ym+4f6zaDYP6B x0r+SaJcr6eSGNm7X3EwX1v7XpRBY+aw019o7k72d0IX910F+XGt0OwNdM61Ff3FiTiexeUZ bWxCGm6GZl+SQVG9xYVIgHQaLXoQF+g2wzrmKCbVcZhqH+hrlRnD6PfCuEyX/BR6PlAPRDlQ 6f1u3wqik+LF5P15AgMBAAGjggNbMIIDVzAMBgNVHRMEBTADAQH/MAsGA1UdDwQEAwIBpjAd BgNVHQ4EFgQUe4mckpckoYRHAst0/C70rNwy5fMwgagGA1UdIwSBoDCBnYAUTgvvGqRAW6UX aYcwyjRoQ9BBrvKhgYGkfzB9MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRk LjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzEpMCcGA1UE AxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHmCAQEwCQYDVR0SBAIwADA9Bggr BgEFBQcBAQQxMC8wLQYIKwYBBQUHMAKGIWh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2Nh LmNydDBgBgNVHR8EWTBXMCygKqAohiZodHRwOi8vY2VydC5zdGFydGNvbS5vcmcvc2ZzY2Et Y3JsLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20vc2ZzY2EuY3JsMIIBXQYD VR0gBIIBVDCCAVAwggFMBgsrBgEEAYG1NwEBBDCCATswLwYIKwYBBQUHAgEWI2h0dHA6Ly9j ZXJ0LnN0YXJ0Y29tLm9yZy9wb2xpY3kucGRmMDUGCCsGAQUFBwIBFilodHRwOi8vY2VydC5z dGFydGNvbS5vcmcvaW50ZXJtZWRpYXRlLnBkZjCB0AYIKwYBBQUHAgIwgcMwJxYgU3RhcnQg Q29tbWVyY2lhbCAoU3RhcnRDb20pIEx0ZC4wAwIBARqBl0xpbWl0ZWQgTGlhYmlsaXR5LCBy ZWFkIHRoZSBzZWN0aW9uICpMZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENl cnRpZmljYXRpb24gQXV0aG9yaXR5IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL2NlcnQu c3RhcnRjb20ub3JnL3BvbGljeS5wZGYwEQYJYIZIAYb4QgEBBAQDAgAHMFAGCWCGSAGG+EIB DQRDFkFTdGFydENvbSBDbGFzcyAzIFByaW1hcnkgSW50ZXJtZWRpYXRlIEZyZWUgU1NMIEVt YWlsIENlcnRpZmljYXRlczANBgkqhkiG9w0BAQUFAAOCAgEAUpcEDdsKFRCxFBxcSm+8oMTT fpS7fbZkxWHx5fHDjvAgaBQ+oY0tk4xtbD6VxeHYjxI63+hj8jICnqeVXPe34Bu+XzekIn2T lrnPCQobKdQF2p52QgUvIxSURed0jcBaCBV22DSKaUqDOzD/Tx6VQy78zpblXjRH7OALE/+H jzJVmspdnBUUtQOLYgPo924xkxR25VDdgtEE5vAXa/g2oCeZhy0ZEO4NbgIayAYCJcJRDz0h dD2Ahec65Kw6LB3N7VXEjiRR5/WoKwH/QteRzPJbFDc1somrApjm2cyg+5nbm1RHeFIz+GxX luRrPztvhNcby0PtAjqwY1txi4sW0R6ZJPuZ2DZ1/dzckoFhyZgFyOX3SEkNXVLldjTzneFJ FnVSzDbc720vq184jR7pYoI9+f5QJ96a0iLxEAG8SJ5auBwXI/w2FmKmwmdMvJ8/17+B4sMC IRrXrDQl2xzpVXh/Qcmk5nf+w8HFmqATGy1OUAQbXga7AySAUaYhvvFk50u0bO5DiUGwzrJO 3TrwvaC2Ei4EFaBmIVgG7TfU5TaaY9IcJSCQ7AGUYE3RFSRpsLOoA3DsxP42YERgS/Nxw29+ YqZtPoO2QPbNpI7xnHVCfNBabx3oDIf438nFfv8spw5BQqBSbEF1izJA57eE64CzHnt7lB20 OFD11avYopwxggPKMIIDxgIBATCBkjCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0 Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcx ODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDMgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50 IENBAgFVMAkGBSsOAwIaBQCgggIMMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZI hvcNAQkFMQ8XDTEwMDYxNjIxMzg1M1owIwYJKoZIhvcNAQkEMRYEFMbL0zjSlpOORd50XysO q6QtGmrXMF8GCSqGSIb3DQEJDzFSMFAwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqG SIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBowYJ KwYBBAGCNxAEMYGVMIGSMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRk LjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UE AxMvU3RhcnRDb20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAVUw gaUGCyqGSIb3DQEJEAILMYGVoIGSMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRD b20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4 MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMyBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQg Q0ECAVUwDQYJKoZIhvcNAQEBBQAEggEAc2oTNVdveWVmtDY4rMBr0EtPUA+kw3COVGWkWMxz V5UWTEl4Qk7j870Z2ZOzHQBmnaaiF8yrMNBAXLkUD7nM4H/HnGZ+xnMs5sqjR9gzor0JSsLC 6dFQl+4XxjIM9Q5Xn7qYanzgqnO7Ln/Pefzndn20kJP9t1pUCse9ZOps/LXlt2hy8R3tcbFU ibyqtfJgNvzLbsWJBznAPjOxtV4DIdt1VfLyw/C8Dk4xB3xjojxjgSJ9KSfEkoougFMMy3ZY J3PGqWWLRDuK5LDKLv64H+QyiyCXLwMQDnCmNmGKSCgWenhyUVjrnotBGw//GOkgbcJ+Rd8a ElzAuVrTQzIX5wAAAAAAAA== --------------ms020504040609050600030806-- From henrik@levkowetz.com Wed Jun 23 05:21:08 2010 Return-Path: X-Original-To: tools-discuss@core3.amsl.com Delivered-To: tools-discuss@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 81E133A68C2 for ; Wed, 23 Jun 2010 05:21:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.926 X-Spam-Level: X-Spam-Status: No, score=-100.926 tagged_above=-999 required=5 tests=[AWL=0.185, BAYES_05=-1.11, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] 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 3aPyDs2HHq58 for ; Wed, 23 Jun 2010 05:21:02 -0700 (PDT) Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by core3.amsl.com (Postfix) with ESMTP id B0A7E3A69BB for ; Wed, 23 Jun 2010 05:20:59 -0700 (PDT) Received: from brunello.autonomica.se ([2a01:3f0:1:0:21e:c2ff:fe13:7e3e]:49701 helo=dyn-fg124.sth.netnod.se) by merlot.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1OROwo-0007vG-LD; Wed, 23 Jun 2010 14:20:55 +0200 Message-ID: <4C21FC26.5040303@levkowetz.com> Date: Wed, 23 Jun 2010 14:20:54 +0200 From: Henrik Levkowetz User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: David Harringoton References: <26D3811086D24939BE02F6A5A9057927@23FX1C1> In-Reply-To: <26D3811086D24939BE02F6A5A9057927@23FX1C1> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 2a01:3f0:1:0:21e:c2ff:fe13:7e3e X-SA-Exim-Rcpt-To: ietfdbh@comcast.net, tools-discuss@ietf.org, henrik-sent@levkowetz.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000) X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org) Cc: tools-discuss@ietf.org Subject: Re: [Tools-discuss] dependencies link X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2010 12:21:08 -0000 Hi David, On 2010-06-14 22:38 David Harringoton said: > Hi, > > In the datatracker, there is a link to "dependencies on this draft". > The link is to Bill's utility, and the utility is not accessible. > I would find it very helpful to have such a dependency tool. > Can the tools team either get Bill's utility made accessible or > develop another dependency tool? Bill's tool seems to be up and running (I checked just now) so this may have been a temporary glitch? Best, Henrik From henrik@levkowetz.com Wed Jun 23 05:24:58 2010 Return-Path: X-Original-To: tools-discuss@core3.amsl.com Delivered-To: tools-discuss@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D49D83A67E9 for ; Wed, 23 Jun 2010 05:24:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.463 X-Spam-Level: X-Spam-Status: No, score=-100.463 tagged_above=-999 required=5 tests=[AWL=-0.463, BAYES_50=0.001, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] 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 vD1V4yKILHee for ; Wed, 23 Jun 2010 05:24:57 -0700 (PDT) Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by core3.amsl.com (Postfix) with ESMTP id DFF3F3A69A3 for ; Wed, 23 Jun 2010 05:24:52 -0700 (PDT) Received: from brunello.autonomica.se ([2a01:3f0:1:0:21e:c2ff:fe13:7e3e]:49710 helo=dyn-fg124.sth.netnod.se) by merlot.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ORP0N-0006vR-N4; Wed, 23 Jun 2010 14:24:40 +0200 Message-ID: <4C21FD03.80702@levkowetz.com> Date: Wed, 23 Jun 2010 14:24:35 +0200 From: Henrik Levkowetz User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: Fred Baker References: <54AFE1A8-8191-4005-ABB0-76AC692F8E99@cisco.com> In-Reply-To: <54AFE1A8-8191-4005-ABB0-76AC692F8E99@cisco.com> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 2a01:3f0:1:0:21e:c2ff:fe13:7e3e X-SA-Exim-Rcpt-To: fred@cisco.com, tools-discuss@ietf.org, draft-ietf-v6ops-cpe-simple-security@tools.ietf.org, draft-ietf-v6ops-ipv6-cpe-router@tools.ietf.org, rbonica@juniper.net, henrik-sent@levkowetz.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000) X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org) Cc: draft-ietf-v6ops-cpe-simple-security@tools.ietf.org, draft-ietf-v6ops-ipv6-cpe-router@tools.ietf.org, IETF TOOLS discussion , Ron Bonica Subject: Re: [Tools-discuss] issue with id-nits X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2010 12:24:58 -0000 Hi, The list of RFC keywords found in --verbose --verbose mode is not in any way an error or warning from idnits, it's just one of many possible verbose messages emitted in the very verbose mode. Only if idnits explicitly indicates a non-zero error or warning count do you have to consider there being errors or warnings associated with the draft. Best, Henrik On 2010-06-04 21:59 Fred Baker said: > Houston, we have a problem... > > The authors of draft-ietf-v6ops-cpe-simple-security and draft-ietf-v6ops-ipv6-cpe-router checked their drafts against http://tools.ietf.org/tools/idnits/ and came up with at most a couple of glitches like > >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(351): Unexpected reference format: '...ent ([RFC4862]/[RFC...' > > When I do the same, I get something like > >> idnits 2.12.04 >> >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt: >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(317): RFC 2119 keyword: G-2: The IPv6 CE router MUST implement ICMP according to [RFC4443].. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(318): RFC 2119 keyword: In particular point to point links MUST be handled as described. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(321): RFC 2119 keyword: G-3: The IPv6 CE router MUST NOT forward any IPv6 traffic between. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(349): RFC 2119 keyword: W-1: When the router is attached to the WAN interface link it MUST. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(351): Unexpected reference format: '...ent ([RFC4862]/[RFC...' >> --> interface address assignment ([RFC4862]/[RFC3315]). >> ^ >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(353): RFC 2119 keyword: W-2: The IPv6 CE router MUST generate a link-local address and. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(356): RFC 2119 keyword: source address used in the subsequent Router Solicitation MUST. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(359): RFC 2119 keyword: W-3: Absent of other routing information the IPv6 CE router MUST use. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(364): RFC 2119 keyword: W-4: The router MUST act as a requesting router for the purposes of. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(368): RFC 2119 keyword: (IA_PD) SHOULD be done as a single DHCPv6 session.. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(373): RFC 2119 keyword: the IPv6 CE router MUST support IPv6 over Ethernet [RFC2464].. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(376): RFC 2119 keyword: router MUST support IPv6 over PPP [RFC5072].. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(380): RFC 2119 keyword: logical channel, the NCPs MUST be treated as independent of. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(396): RFC 2119 keyword: WAA-1: The IPv6 CE router MUST support SLAAC [RFC4862].. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(398): RFC 2119 keyword: WAA-2: The IPv6 CE router MUST follow the recommendation in. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(403): RFC 2119 keyword: WAA-3: The IPv6 CE router MUST support DHCPv6 [RFC3315] client. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(406): RFC 2119 keyword: WAA-4: The IPv6 CE router MUST be able to support the following. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(410): RFC 2119 keyword: WAA-5: The IPv6 CE router SHOULD support the DHCPv6 SNTP option. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(414): RFC 2119 keyword: [RFC4861]) with the M-flag set to 1, the IPv6 CE router MUST. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(418): RFC 2119 keyword: SLAAC it MAY do DHCPv6 address assignment (request an IA_NA). >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(422): RFC 2119 keyword: address(es) from either SLAAC or DHCPv6, then it MUST create. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(427): RFC 2119 keyword: WAA-9: As a router the IPv6 CE router MUST follow the weak host. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(435): RFC 2119 keyword: WPD-1: The IPv6 CE router MUST support DHCPv6 prefix delegation. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(439): RFC 2119 keyword: WPD-2: The IPv6 CE router MAY indicate as a hint to the delegating. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(440): RFC 2119 keyword: router the size of the prefix it requires. If so, it MUST. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(442): RFC 2119 keyword: its interfaces rounded up to the nearest nibble and MUST be. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(452): RFC 2119 keyword: WPD-3: The IPv6 CE router MUST be prepared to accept a delegated. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(455): RFC 2119 keyword: interfaces, the IPv6 CE router SHOULD log a system management. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(458): RFC 2119 keyword: WPD-4: The IPv6 CE router MUST always initiate DHCPv6 prefix. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(463): RFC 2119 keyword: Router Advertisement it MUST also request an IA_NA option in. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(467): RFC 2119 keyword: multiple, more-specific routes, the IPv6 CE router MUST. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(475): RFC 2119 keyword: (a) The IPv6 CE router SHOULD send an ICMPv6 Destination. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(481): RFC 2119 keyword: DHCPv6, it MUST accept an IA_PD in DHCPv6 Advertise/Reply. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(485): RFC 2119 keyword: WPD-8: By default an IPv6 CE router MUST NOT initiate any dynamic. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(525): RFC 2119 keyword: L-1: The IPv6 CE router MUST support ULA addressing [RFC4193].. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(527): RFC 2119 keyword: L-2: The IPv6 CE router MUST have a ULA prefix that it maintains. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(530): RFC 2119 keyword: L-3: The value of the ULA prefix SHOULD be user configurable.. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(532): RFC 2119 keyword: L-4: By default the IPv6 CE router MUST act as a site border router. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(536): RFC 2119 keyword: L-5: The IPv6 CE router MUST support router behavior according to. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(539): RFC 2119 keyword: L-6: The IPv6 CE router MUST assign a separate /64 from its. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(543): RFC 2119 keyword: L-7: The IPv6 CE router MUST make each LAN interface an advertising. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(547): RFC 2119 keyword: Option's A and L-flags MUST be set to 1 by default.. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(549): RFC 2119 keyword: L-9: The A and L-flags setting SHOULD be user configurable.. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(551): RFC 2119 keyword: L-10: The IPv6 CE router MUST support a DHCPv6 server capable of. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(565): RFC 2119 keyword: IA_NA option, it SHOULD set M=0 and O=1 in its Router. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(568): RFC 2119 keyword: L-12: The IPv6 CE router MUST support providing DNS information in. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(571): RFC 2119 keyword: L-13: The IPv6 CE router SHOULD make available a subset of DHCPv6. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(578): RFC 2119 keyword: period, then the IPv6 CE router MUST immediately advertise the. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(583): RFC 2119 keyword: L-15: The IPv6 CE router MUST send an ICMP Destination Unreachable. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(600): RFC 2119 keyword: S-1: The IPv6 CE router SHOULD support. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(603): RFC 2119 keyword: S-2: The IPv6 CE router MUST support ingress filtering in accordance. >> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(604): Unexpected reference format: '...with [RFC2827](BCP ...' >> --> with [RFC2827](BCP 38) > > The file contains the specified reference to RFC 2119, in section 1.1 in both cases, and we are using the same version of the checker. > > Help? I'm going to file the report saying that id-nits is wrong, which I would rather not do. > _______________________________________________ > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/tools-discuss > From henrik@levkowetz.com Wed Jun 23 05:33:10 2010 Return-Path: X-Original-To: tools-discuss@core3.amsl.com Delivered-To: tools-discuss@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E956A3A6A02 for ; Wed, 23 Jun 2010 05:33:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.609 X-Spam-Level: X-Spam-Status: No, score=-101.609 tagged_above=-999 required=5 tests=[AWL=0.991, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] 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 dV6P-zPoByED for ; Wed, 23 Jun 2010 05:33:06 -0700 (PDT) Received: from merlot.tools.ietf.org (merlot.tools.ietf.org [IPv6:2a01:3f0:0:31:214:22ff:fe21:bb]) by core3.amsl.com (Postfix) with ESMTP id 073E03A69F6 for ; Wed, 23 Jun 2010 05:33:06 -0700 (PDT) Received: from brunello.autonomica.se ([2a01:3f0:1:0:21e:c2ff:fe13:7e3e]:49737 helo=dyn-fg124.sth.netnod.se) by merlot.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ORP8G-0003b5-Aa; Wed, 23 Jun 2010 14:32:50 +0200 Message-ID: <4C21FEEB.8070201@levkowetz.com> Date: Wed, 23 Jun 2010 14:32:43 +0200 From: Henrik Levkowetz User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: Spencer Dawkins References: <4C17D3D0.2030605@innovationslab.net> <8C2D6032405045D0AA6E2C9A21EA475C@china.huawei.com> In-Reply-To: <8C2D6032405045D0AA6E2C9A21EA475C@china.huawei.com> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 2a01:3f0:1:0:21e:c2ff:fe13:7e3e X-SA-Exim-Rcpt-To: spencer@wonderhamster.org, brian@innovationslab.net, tools-discuss@ietf.org, henrik-sent@levkowetz.com X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000) X-SA-Exim-Scanned: Yes (on merlot.tools.ietf.org) Cc: Brian Haberman , IETF TOOLS discussion Subject: Re: [Tools-discuss] Concluded working groups page seems to be broken X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2010 12:33:10 -0000 Hi Spencer, On 2010-06-16 01:07 Spencer Dawkins said: > OK, I couldn't be more mystified. The links in the list of concluded WGs were wrong, pointing to http://tools.ietf.org/wg/concluded/ instead of http://tools.ietf.org/wg/ . I've fixed the script producing the list of concluded WGs to show the correct URL, and added redirects from the incorrect locations to the correct ones. Best, Henri >> Spencer, >> Seems to work for me using http://tools.ietf.org/wg/provreg/. >> >> Brian > > But it's working for me now - thanks! > > Spencer > >> On 6/15/10 3:18 PM, Spencer Dawkins wrote: >>> Hi, >>> >>> When I click on http://tools.ietf.org/wg/concluded/provreg, it is just >>> showing me the list of all concluded working groups - no detail on >>> provreg itself. >>> >>> It should be showing me things like the charter when the working group >>> was concluded, the RFCs produced, etc. >>> >>> This seems to be true for other concluded working groups as well. >>> >>> Thanks, >>> >>> Spencer >>> _______________________________________________ >>> Tools-discuss mailing list >>> Tools-discuss@ietf.org >>> https://www.ietf.org/mailman/listinfo/tools-discuss >> > _______________________________________________ > Tools-discuss mailing list > Tools-discuss@ietf.org > https://www.ietf.org/mailman/listinfo/tools-discuss > From spencer@wonderhamster.org Wed Jun 23 07:27:22 2010 Return-Path: X-Original-To: tools-discuss@core3.amsl.com Delivered-To: tools-discuss@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F68A3A6359 for ; Wed, 23 Jun 2010 07:27:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.08 X-Spam-Level: X-Spam-Status: No, score=-0.08 tagged_above=-999 required=5 tests=[AWL=0.104, BAYES_40=-0.185, STOX_REPLY_TYPE=0.001] 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 3OhCC8NW76nS for ; Wed, 23 Jun 2010 07:27:21 -0700 (PDT) Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by core3.amsl.com (Postfix) with ESMTP id A1E143A677D for ; Wed, 23 Jun 2010 07:27:21 -0700 (PDT) Received: from S73602b (cpe-76-182-230-135.tx.res.rr.com [76.182.230.135]) by mrelay.perfora.net (node=mrus4) with ESMTP (Nemesis) id 0LiDT1-1Ow6zA3WDb-00mx9N; Wed, 23 Jun 2010 10:27:28 -0400 Message-ID: From: "Spencer Dawkins" To: "Henrik Levkowetz" References: <4C17D3D0.2030605@innovationslab.net> <8C2D6032405045D0AA6E2C9A21EA475C@china.huawei.com> <4C21FEEB.8070201@levkowetz.com> Date: Wed, 23 Jun 2010 09:27:15 -0500 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931 X-Provags-ID: V01U2FsdGVkX1+9W8byeDz1uNp3/Csp9200l/3iu50pCMmO/rj Aj5WL0KlUaWkqZ95aUgw4CIxJoJGB2ZnvB7C4VfHM3iqgDe62z JLvm3WWxIaoJNjB7c1OI+BRxbXBb/ZJzYYaKQDbgUU= Cc: Brian Haberman , IETF TOOLS discussion Subject: Re: [Tools-discuss] Concluded working groups page seems to be broken X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2010 14:27:22 -0000 Henrik, Thank you for fixing this! Spencer > Hi Spencer, > > On 2010-06-16 01:07 Spencer Dawkins said: >> OK, I couldn't be more mystified. > > The links in the list of concluded WGs were wrong, pointing to > > http://tools.ietf.org/wg/concluded/ > instead of > http://tools.ietf.org/wg/ > . > > I've fixed the script producing the list of concluded WGs to show > the correct URL, and added redirects from the incorrect locations > to the correct ones. > > > Best, > > Henri > > > >>> Spencer, >>> Seems to work for me using http://tools.ietf.org/wg/provreg/. >>> >>> Brian >> >> But it's working for me now - thanks! >> >> Spencer >> >>> On 6/15/10 3:18 PM, Spencer Dawkins wrote: >>>> Hi, >>>> >>>> When I click on http://tools.ietf.org/wg/concluded/provreg, it is just >>>> showing me the list of all concluded working groups - no detail on >>>> provreg itself. >>>> >>>> It should be showing me things like the charter when the working group >>>> was concluded, the RFCs produced, etc. >>>> >>>> This seems to be true for other concluded working groups as well. >>>> >>>> Thanks, >>>> >>>> Spencer >>>> _______________________________________________ >>>> Tools-discuss mailing list >>>> Tools-discuss@ietf.org >>>> https://www.ietf.org/mailman/listinfo/tools-discuss >>> >> _______________________________________________ >> Tools-discuss mailing list >> Tools-discuss@ietf.org >> https://www.ietf.org/mailman/listinfo/tools-discuss >> From fred@cisco.com Wed Jun 23 15:29:35 2010 Return-Path: X-Original-To: tools-discuss@core3.amsl.com Delivered-To: tools-discuss@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DDB9D3A67D1 for ; Wed, 23 Jun 2010 15:29:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -110.599 X-Spam-Level: X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100] 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 R0snzv09z-Ta for ; Wed, 23 Jun 2010 15:29:33 -0700 (PDT) Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 1DA593A6844 for ; Wed, 23 Jun 2010 15:29:33 -0700 (PDT) Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAA0oIkxAZnwM/2dsb2JhbACfMnGoeppHhRsE X-IronPort-AV: E=Sophos;i="4.53,469,1272844800"; d="scan'208";a="124922133" Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-2.cisco.com with ESMTP; 23 Jun 2010 22:29:36 +0000 Received: from dhcp-10-59-1-37.cisco.com (dhcp-10-55-94-28.cisco.com [10.55.94.28]) by rtp-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o5NMTOwR010835; Wed, 23 Jun 2010 22:29:26 GMT Received: from [127.0.0.1] by dhcp-10-59-1-37.cisco.com (PGP Universal service); Thu, 24 Jun 2010 00:29:33 +0200 X-PGP-Universal: processed; by dhcp-10-59-1-37.cisco.com on Thu, 24 Jun 2010 00:29:33 +0200 Mime-Version: 1.0 (Apple Message framework v1081) From: Fred Baker In-Reply-To: <4C21FD03.80702@levkowetz.com> Date: Thu, 24 Jun 2010 00:29:18 +0200 Message-Id: References: <54AFE1A8-8191-4005-ABB0-76AC692F8E99@cisco.com> <4C21FD03.80702@levkowetz.com> To: Henrik Levkowetz X-Mailer: Apple Mail (2.1081) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: draft-ietf-v6ops-cpe-simple-security@tools.ietf.org, draft-ietf-v6ops-ipv6-cpe-router@tools.ietf.org, IETF TOOLS discussion , Ron Bonica Subject: Re: [Tools-discuss] issue with id-nits X-BeenThere: tools-discuss@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF Tools Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jun 2010 22:29:36 -0000 Thanks. That's not obvious from the output. On Jun 23, 2010, at 2:24 PM, Henrik Levkowetz wrote: > Hi, >=20 > The list of RFC keywords found in --verbose --verbose mode is not in = any > way an error or warning from idnits, it's just one of many possible = verbose > messages emitted in the very verbose mode. >=20 > Only if idnits explicitly indicates a non-zero error or warning count = do > you have to consider there being errors or warnings associated with = the > draft. >=20 >=20 > Best, >=20 > Henrik >=20 > On 2010-06-04 21:59 Fred Baker said: >> Houston, we have a problem... >>=20 >> The authors of draft-ietf-v6ops-cpe-simple-security and = draft-ietf-v6ops-ipv6-cpe-router checked their drafts against = http://tools.ietf.org/tools/idnits/ and came up with at most a couple of = glitches like=20 >>=20 >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(351): Unexpected = reference format: '...ent ([RFC4862]/[RFC...' >>=20 >> When I do the same, I get something like >>=20 >>> idnits 2.12.04=20 >>>=20 >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt: >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(317): RFC 2119 keyword: = G-2: The IPv6 CE router MUST implement ICMP according to [RFC4443].. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(318): RFC 2119 keyword: = In particular point to point links MUST be handled as described. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(321): RFC 2119 keyword: = G-3: The IPv6 CE router MUST NOT forward any IPv6 traffic between. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(349): RFC 2119 keyword: = W-1: When the router is attached to the WAN interface link it MUST. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(351): Unexpected = reference format: '...ent ([RFC4862]/[RFC...' >>> --> interface address assignment ([RFC4862]/[RFC3315]). >>> ^ >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(353): RFC 2119 keyword: = W-2: The IPv6 CE router MUST generate a link-local address and. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(356): RFC 2119 keyword: = source address used in the subsequent Router Solicitation MUST. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(359): RFC 2119 keyword: = W-3: Absent of other routing information the IPv6 CE router MUST use. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(364): RFC 2119 keyword: = W-4: The router MUST act as a requesting router for the purposes of. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(368): RFC 2119 keyword: = (IA_PD) SHOULD be done as a single DHCPv6 session.. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(373): RFC 2119 keyword: = the IPv6 CE router MUST support IPv6 over Ethernet [RFC2464].. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(376): RFC 2119 keyword: = router MUST support IPv6 over PPP [RFC5072].. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(380): RFC 2119 keyword: = logical channel, the NCPs MUST be treated as independent of. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(396): RFC 2119 keyword: = WAA-1: The IPv6 CE router MUST support SLAAC [RFC4862].. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(398): RFC 2119 keyword: = WAA-2: The IPv6 CE router MUST follow the recommendation in. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(403): RFC 2119 keyword: = WAA-3: The IPv6 CE router MUST support DHCPv6 [RFC3315] client. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(406): RFC 2119 keyword: = WAA-4: The IPv6 CE router MUST be able to support the following. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(410): RFC 2119 keyword: = WAA-5: The IPv6 CE router SHOULD support the DHCPv6 SNTP option. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(414): RFC 2119 keyword: = [RFC4861]) with the M-flag set to 1, the IPv6 CE router MUST. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(418): RFC 2119 keyword: = SLAAC it MAY do DHCPv6 address assignment (request an IA_NA). >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(422): RFC 2119 keyword: = address(es) from either SLAAC or DHCPv6, then it MUST create. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(427): RFC 2119 keyword: = WAA-9: As a router the IPv6 CE router MUST follow the weak host. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(435): RFC 2119 keyword: = WPD-1: The IPv6 CE router MUST support DHCPv6 prefix delegation. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(439): RFC 2119 keyword: = WPD-2: The IPv6 CE router MAY indicate as a hint to the delegating. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(440): RFC 2119 keyword: = router the size of the prefix it requires. If so, it MUST. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(442): RFC 2119 keyword: = its interfaces rounded up to the nearest nibble and MUST be. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(452): RFC 2119 keyword: = WPD-3: The IPv6 CE router MUST be prepared to accept a delegated. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(455): RFC 2119 keyword: = interfaces, the IPv6 CE router SHOULD log a system management. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(458): RFC 2119 keyword: = WPD-4: The IPv6 CE router MUST always initiate DHCPv6 prefix. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(463): RFC 2119 keyword: = Router Advertisement it MUST also request an IA_NA option in. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(467): RFC 2119 keyword: = multiple, more-specific routes, the IPv6 CE router MUST. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(475): RFC 2119 keyword: = (a) The IPv6 CE router SHOULD send an ICMPv6 Destination. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(481): RFC 2119 keyword: = DHCPv6, it MUST accept an IA_PD in DHCPv6 Advertise/Reply. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(485): RFC 2119 keyword: = WPD-8: By default an IPv6 CE router MUST NOT initiate any dynamic. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(525): RFC 2119 keyword: = L-1: The IPv6 CE router MUST support ULA addressing [RFC4193].. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(527): RFC 2119 keyword: = L-2: The IPv6 CE router MUST have a ULA prefix that it maintains. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(530): RFC 2119 keyword: = L-3: The value of the ULA prefix SHOULD be user configurable.. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(532): RFC 2119 keyword: = L-4: By default the IPv6 CE router MUST act as a site border router. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(536): RFC 2119 keyword: = L-5: The IPv6 CE router MUST support router behavior according to. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(539): RFC 2119 keyword: = L-6: The IPv6 CE router MUST assign a separate /64 from its. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(543): RFC 2119 keyword: = L-7: The IPv6 CE router MUST make each LAN interface an advertising. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(547): RFC 2119 keyword: = Option's A and L-flags MUST be set to 1 by default.. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(549): RFC 2119 keyword: = L-9: The A and L-flags setting SHOULD be user configurable.. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(551): RFC 2119 keyword: = L-10: The IPv6 CE router MUST support a DHCPv6 server capable of. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(565): RFC 2119 keyword: = IA_NA option, it SHOULD set M=3D0 and O=3D1 in its Router. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(568): RFC 2119 keyword: = L-12: The IPv6 CE router MUST support providing DNS information in. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(571): RFC 2119 keyword: = L-13: The IPv6 CE router SHOULD make available a subset of DHCPv6. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(578): RFC 2119 keyword: = period, then the IPv6 CE router MUST immediately advertise the. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(583): RFC 2119 keyword: = L-15: The IPv6 CE router MUST send an ICMP Destination Unreachable. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(600): RFC 2119 keyword: = S-1: The IPv6 CE router SHOULD support. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(603): RFC 2119 keyword: = S-2: The IPv6 CE router MUST support ingress filtering in accordance. >>> tmp/draft-ietf-v6ops-ipv6-cpe-router-05.txt(604): Unexpected = reference format: '...with [RFC2827](BCP ...' >>> --> with [RFC2827](BCP 38) >>=20 >> The file contains the specified reference to RFC 2119, in section 1.1 = in both cases, and we are using the same version of the checker. >>=20 >> Help? I'm going to file the report saying that id-nits is wrong, = which I would rather not do. >> _______________________________________________ >> Tools-discuss mailing list >> Tools-discuss@ietf.org >> https://www.ietf.org/mailman/listinfo/tools-discuss >>=20 http://www.ipinc.net/IPv4.GIF