BEEP Document Comments (was RE: July milestones)
"Hollenbeck, Scott" <shollenbeck@verisign.com> Fri, 26 July 2002 16:39 UTC
Received: from nic.cafax.se (nic.cafax.se [192.71.228.17]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29074 for <provreg-archive@ietf.org>; Fri, 26 Jul 2002 12:39:48 -0400 (EDT)
Received: from nic.cafax.se (localhost [127.0.0.1]) by nic.cafax.se (8.12.5/8.12.5) with ESMTP id g6QGYXo2003648 for <ietf-provreg-outgoing@nic.cafax.se>; Fri, 26 Jul 2002 18:34:33 +0200 (MEST)
Received: by nic.cafax.se (8.12.5/8.12.5/Submit) id g6QGYXtq003647 for ietf-provreg-outgoing; Fri, 26 Jul 2002 18:34:33 +0200 (MEST)
X-Authentication-Warning: nic.cafax.se: majordom set sender to owner-ietf-provreg@cafax.se using -f
Received: from heron.verisign.com (heron.verisign.com [216.168.233.95]) by nic.cafax.se (8.12.5/8.12.5) with ESMTP id g6QGYWo2003642 for <ietf-provreg@cafax.se>; Fri, 26 Jul 2002 18:34:32 +0200 (MEST)
Received: from VSVAPOSTALGW1.prod.netsol.com (vsvapostalgw1.prod.netsol.com [216.168.234.201]) by heron.verisign.com (nsi_0.1/8.9.1) with ESMTP id MAA09336; Fri, 26 Jul 2002 12:35:14 -0400 (EDT)
Received: by VSVAPOSTALGW1.prod.netsol.com with Internet Mail Service (5.5.2653.19) id <NJVGLVWX>; Fri, 26 Jul 2002 12:34:26 -0400
Message-ID: <3CD14E451751BD42BA48AAA50B07BAD60189BCC4@vsvapostal3.prod.netsol.com>
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: 'Edward Lewis' <edlewis@arin.net>, jaap@sidn.nl
Cc: ietf-provreg@cafax.se
Subject: BEEP Document Comments (was RE: July milestones)
Date: Fri, 26 Jul 2002 12:34:26 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Sender: owner-ietf-provreg@cafax.se
Precedence: bulk
> Well, we do have some current comments on the document...but Rick's > question is still germane, what community is forming around a BEEP > transport for EPP? There are also some old comments that haven't been completely addressed: http://www.cafax.se/ietf-provreg/maillist/2001-09/msg00010.html Specifically, the TCP transport clarification and "Content-Type: text/xml" comments. Also, the IESG is getting picky about splitting references into normative and informative subsections, so that should be done in the document. New comment/thought: would it be wise to consider Marshall's transient profile identifier ideas, described here:? http://www.ietf.org/internet-drafts/draft-mrose-beep-transientid-02.txt -Scott-
- BEEP Document Comments (was RE: July milestones) Hollenbeck, Scott
- RE: BEEP Document Comments (was RE: July mileston… Zhang, Ning