Re: [sidr] Working Group Last Call - draft-ietf-sidr-arch-09.txt

To: George Michaelson <ggm at apnic.net>
Subject: Re: [sidr] Working Group Last Call - draft-ietf-sidr-arch-09.txt
From: Randy Bush <randy at psg.com>
Date: Fri, 30 Oct 2009 07:09:36 +0900
Cc: sidr <sidr at ietf.org>
Delivered-to: sidr at core3.amsl.com
In-reply-to: <DB701F0C-B9D7-4CF7-ACDE-2D5C387EB9D7 at apnic.net>
List-archive: <http://www.ietf.org/mail-archive/web/sidr>
List-help: <mailto:sidr-request@ietf.org?subject=help>
List-id: Secure Interdomain Routing <sidr.ietf.org>
List-post: <mailto:sidr@ietf.org>
List-subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
References: <1CCB8133-6C27-480B-8A9A-196927F526C9 at apnic.net> <DB701F0C-B9D7-4CF7-ACDE-2D5C387EB9D7 at apnic.net>
User-agent: Wanderlust/2.15.5 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)

> I believe the document needs to have the 3 hour time cycle removed,  
> and some form of operational guidelines placed in a distinct document  
> (whether 3 hours, or some other time, is up to that document)

i suspect it belongs in the CP, but am not sure.

randy

Follow-Ups:
- Re: [sidr] Working Group Last Call - draft-ietf-sidr-arch-09.txt
  - From: Stephen Kent

References:
- [sidr] Working Group Last Call - draft-ietf-sidr-arch-09.txt
  - From: Geoff Huston
- Re: [sidr] Working Group Last Call - draft-ietf-sidr-arch-09.txt
  - From: George Michaelson

Prev by Date: [sidr] Working Group Last Call - draft-ietf-sidr-rescerts-provisioning-05.txt
Next by Date: Re: [sidr] sidr-arch-09 refresh cycle time
Previous by thread: Re: [sidr] Working Group Last Call - draft-ietf-sidr-arch-09.txt
Next by thread: Re: [sidr] Working Group Last Call - draft-ietf-sidr-arch-09.txt
Index(es):
- Date
- Thread

Re: [sidr] Working Group Last Call - draft-ietf-sidr-arch-09.txt

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.