From techspec-bounces@ietf.org Mon Jul 10 19:37:01 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G05JD-0001zh-Cd; Mon, 10 Jul 2006 19:36:59 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G05JC-0001zW-NX for techspec@ietf.org; Mon, 10 Jul 2006 19:36:58 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FzvE3-00036q-F3; Mon, 10 Jul 2006 08:50:59 -0400 Received: from smtp121.iad.emailsrvr.com ([207.97.245.121]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FzuvB-0008Gm-IN; Mon, 10 Jul 2006 08:31:31 -0400 Received: from [132.219.27.223] (unknown [132.219.27.223]) (Authenticated sender: rpelletier@isoc.org) by relay2.r2.iad.emailsrvr.com (SMTP Server) with ESMTP id E76A644C0C7; Mon, 10 Jul 2006 08:31:28 -0400 (EDT) Message-ID: <44B2497D.3060000@isoc.org> Date: Mon, 10 Jul 2006 08:35:09 -0400 From: Ray Pelletier User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: IETF Discussion , 66attendees@ietf.org, The IESG , IAB , IAOC , techspec@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: OK X-Spam-Score: -1.9 (-) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Cc: Subject: [Techspec] RFC Editor SOW Review X-BeenThere: techspec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion list for IETF Technical Specifications \(BOF at IETF64\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: techspec-bounces@ietf.org All; The IAOC intends to promulgate an RFP for the RFC Editor function not later than 31 July 2006. To that end we seek comments on the Statement of Work located at: http://koi.uoregon.edu/~iaoc/ This Statement of Work is a draft and will be updated to conform to the final form of draft-mankin-pub-req for the Request for Proposal. Comments on this Statement of Work should be submitted by 17 July to ensure consideration before promulgation. Thanks for your assistance. Regards Ray Pelletier IETF Administrative Director _______________________________________________ Techspec mailing list Techspec@ietf.org https://www1.ietf.org/mailman/listinfo/techspec From techspec-bounces@ietf.org Wed Jul 12 15:40:12 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0kZ8-000052-3o; Wed, 12 Jul 2006 15:40:10 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G0kZ7-0008WN-A9; Wed, 12 Jul 2006 15:40:09 -0400 Received: from imr2.ericy.com ([198.24.6.3]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0kZ5-0004MI-Sz; Wed, 12 Jul 2006 15:40:09 -0400 Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr2.ericy.com (8.13.1/8.13.1) with ESMTP id k6CJrdvV015008; Wed, 12 Jul 2006 14:53:39 -0500 Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.56]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 12 Jul 2006 14:40:07 -0500 Received: from EBRSPMW720.eamcs.ericsson.se ([146.250.159.54]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 12 Jul 2006 14:40:07 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Wed, 12 Jul 2006 16:39:59 -0300 Message-ID: <4DCBC973AF0D6E4FAF9CD998CE1C003803411B1B@eusrcmw720.eamcs.ericsson.se> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-mankin-pub-req-10 Thread-Index: Acal6vYuynRDLijLQVOHOWXFNfEi5Q== From: "Stephen Hayes \(PL/EUS\)" To: , X-OriginalArrivalTime: 12 Jul 2006 19:40:07.0090 (UTC) FILETIME=[FA89C120:01C6A5EA] X-Spam-Score: 0.1 (/) X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135 Cc: Subject: [Techspec] draft-mankin-pub-req-10 X-BeenThere: techspec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion list for IETF Technical Specifications \(BOF at IETF64\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: techspec-bounces@ietf.org A new version of the technical publisher requirements is available: = http://www.ietf.org/internet-drafts/draft-mankin-pub-req-10.txt This version hopefully resolves a few belated last call comments as well = as the IESG discusses. Stephen Hayes The changes from version 09->10 are: 1. Changes to section 1 (intro): - "ISD" replaced by "otherwise"=20 - It was indicated this document will be used in the preparation of = future contracts - Clarified that the current technical publisher is the RFC Editor 2. Changes to section 2 (scope) - Genericized "RFC streams" to "publication streams" - Added the IETF secretariat and draft publication, status tracking = into the lifecycle diagram 3. Clarified in section 3.1 that the publisher should be capable of = doing pre-approval review, not that it is currently expected to. Also = removed the bias of pre -vs- post-approval editing in sections 3.1 and = 3.3. 4. Clarified in section 3.2 that the publisher is not expected to extend = the lifetime of a draft that is in the publication process. 5. Clarified in section 3.4 that the publisher should only hold up = publication for normative references. 6. Clarified in section 3.5 that the publisher should only do a = syntactic review of formal language sections. 7. Clarified in section 3.7 (Req-POSTCORR-2) that the responsible party = is designated by the IESG and is sometimes referred to as the document = shepherd who is currently an AD. 8. Cleaned up in section 3.9 the formats currently accepted by and = produced by the RFC editor (text has been reviewed by the RFC editor). = Also clarified that it is not the publisher's responsibility to edit = supplemental files. 9. Added to sections 3.11 and 3.16 that it was desirable that the = interface to the status info and the index be documented to facilitate = tool development (indicated as desirable so not a hard requirement). 10. In section 3.13, indicated that the IAB can also put a document on = hold in case of appeal. 11. Clarified in section 3.15 that the process for reviewing, updating, = and approving errata (for IETF documents) is a process issue to be = defined by the IETF. 12. In section 3.16, removed requirement Req-INDEX-7 (to purge a = document). Performing such an action would be due to a legal mandate. = The publisher is expected to comply with legal edicts as much as = possible in any case and it is the contract that should enforce this = behaviour (a requirement to comply with applicable laws seems = unnecessary). Such a hypothetical mandate need not, however, drive = solutions for archiving documents. 13. More editorial cleanup. _______________________________________________ Techspec mailing list Techspec@ietf.org https://www1.ietf.org/mailman/listinfo/techspec From techspec-bounces@ietf.org Thu Jul 13 11:09:18 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G12oY-0004Lu-Jt; Thu, 13 Jul 2006 11:09:18 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G12oU-0004Jj-Pf; Thu, 13 Jul 2006 11:09:14 -0400 Received: from [132.219.31.84] (helo=carter-zimmerman.mit.edu) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G12nv-0008Tp-1o; Thu, 13 Jul 2006 11:08:40 -0400 Received: by carter-zimmerman.mit.edu (Postfix, from userid 8042) id D323FE0079; Thu, 13 Jul 2006 11:08:59 -0400 (EDT) From: Sam Hartman To: Stewart Bryant References: <44B2497D.3060000@isoc.org> <44B657C4.60102@cisco.com> Date: Thu, 13 Jul 2006 11:08:59 -0400 In-Reply-To: <44B657C4.60102@cisco.com> (Stewart Bryant's message of "Thu, 13 Jul 2006 15:25:08 +0100") Message-ID: User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.4 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.1 (/) X-Scan-Signature: 8ac499381112328dd60aea5b1ff596ea Cc: IAB , IETF Discussion , techspec@ietf.org, IAOC , The IESG Subject: [Techspec] Re: RFC Editor SOW Review X-BeenThere: techspec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion list for IETF Technical Specifications \(BOF at IETF64\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: techspec-bounces@ietf.org I do not support Stewart's comment. However I will note that our current process requires the rfc-editor to accept ASCII input along with non-normative PDF or PostScript input. The SOW should reflect this current practice. _______________________________________________ Techspec mailing list Techspec@ietf.org https://www1.ietf.org/mailman/listinfo/techspec From techspec-bounces@ietf.org Thu Jul 13 13:53:29 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G15NQ-0007Ry-PJ; Thu, 13 Jul 2006 13:53:28 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G15NO-0007QX-5b; Thu, 13 Jul 2006 13:53:26 -0400 Received: from mailgw4.ericsson.se ([193.180.251.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G15NM-0001iR-ES; Thu, 13 Jul 2006 13:53:26 -0400 Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id B8F106E0001; Thu, 13 Jul 2006 19:22:14 +0200 (CEST) Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 13 Jul 2006 19:22:14 +0200 Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.51]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 13 Jul 2006 19:22:14 +0200 Received: from EBRSPMW720.eamcs.ericsson.se ([146.250.159.54]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 13 Jul 2006 12:21:56 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Thu, 13 Jul 2006 14:21:17 -0300 Message-ID: <4DCBC973AF0D6E4FAF9CD998CE1C00380343F99F@eusrcmw720.eamcs.ericsson.se> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: RFC Editor SOW Review Thread-Index: Acamjmo8mcd9Wr/7Q++Pk0pYhcyn2wAEQmmQ From: "Stephen Hayes \(PL/EUS\)" To: "Stewart Bryant" X-OriginalArrivalTime: 13 Jul 2006 17:21:56.0806 (UTC) FILETIME=[D78E8E60:01C6A6A0] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Cc: IAOC , IAB , IETF Discussion , techspec@ietf.org, The IESG Subject: [Techspec] RE: RFC Editor SOW Review X-BeenThere: techspec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion list for IETF Technical Specifications \(BOF at IETF64\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: techspec-bounces@ietf.org Stewart Bryand wrote: > Looking at the SOW again, it seems to completely ignore RFC2223.txt > section 1 that says: >=20 > "While the primary RFCs is always an ASCII text file, secondary or > alternative versions of RFC may be provided in PostScript. This > decision is motivated by the desire to include diagrams, drawings, > and such in RFCs. PostScript documents (on paper only, so far) are > visually more appealing and have better readability." >=20 > and also >=20 >=20 much of the text in the SOW is derived from mankin-pub-req. Previous = versions of mankin-pub-req were unclear on whether alternative formats = with better graphics were to be supported. The current version = http://www.ietf.org/internet-drafts/draft-mankin-pub-req-10.txt makes = this explicit by adding the sentence "Supplemental files may also = include enhanced versions of the document containing graphics or = sections not presentable in text format." to section 3.9. My assumption = is that future versions of the SOW will pick this up. mankin-pub-req also has requirements that the publisher support process = change and process experiments (See 3.20). I believe this would address = the desire to have the publisher work with the IETF to allow new formats = should the IETF decide to do so. These requirements however are not = currently reflected in the SOW. Stephen Hayes _______________________________________________ Techspec mailing list Techspec@ietf.org https://www1.ietf.org/mailman/listinfo/techspec From techspec-bounces@ietf.org Thu Jul 13 14:13:36 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G15gu-00021Q-32; Thu, 13 Jul 2006 14:13:36 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G15gr-0001xb-HC; Thu, 13 Jul 2006 14:13:33 -0400 Received: from mtagate6.uk.ibm.com ([195.212.29.139]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G15gq-0003Hh-4N; Thu, 13 Jul 2006 14:13:33 -0400 Received: from d06nrmr1407.portsmouth.uk.ibm.com (d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185]) by mtagate6.uk.ibm.com (8.13.6/8.13.6) with ESMTP id k6DIDVwn122824 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 13 Jul 2006 18:13:31 GMT Received: from d06av04.portsmouth.uk.ibm.com (d06av04.portsmouth.uk.ibm.com [9.149.37.216]) by d06nrmr1407.portsmouth.uk.ibm.com (8.13.6/NCO/VER7.0) with ESMTP id k6DIF3uo128404 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 Jul 2006 19:15:03 +0100 Received: from d06av04.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av04.portsmouth.uk.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id k6DIDUYZ016467; Thu, 13 Jul 2006 19:13:30 +0100 Received: from mail-gw3.hursley.ibm.com (mail-gw3.hursley.ibm.com [9.20.131.251]) by d06av04.portsmouth.uk.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k6DIDUBC016464; Thu, 13 Jul 2006 19:13:30 +0100 Received: from [9.20.118.16] (helo=bf1v5-118.hursley.ibm.com) by mail-gw3.hursley.ibm.com with esmtp (Exim 4.50) id 1G15go-0004HV-6M; Thu, 13 Jul 2006 19:13:30 +0100 Received: from zurich.ibm.com (sig-9-145-255-41.de.ibm.com [9.145.255.41]) by bf1v5-118.hursley.ibm.com (AIX5.3/8.11.6p2/8.11.0) with SMTP id k6DIDS53727408; Thu, 13 Jul 2006 19:13:28 +0100 Message-ID: <44B68D49.80505@zurich.ibm.com> Date: Thu, 13 Jul 2006 20:13:29 +0200 From: Brian E Carpenter Organization: IBM User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en, fr, de MIME-Version: 1.0 To: Sam Hartman References: <44B2497D.3060000@isoc.org> <44B657C4.60102@cisco.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Cc: IAB , IETF Discussion , techspec@ietf.org, IAOC , The IESG , Stewart Bryant Subject: [Techspec] Re: RFC Editor SOW Review X-BeenThere: techspec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion list for IETF Technical Specifications \(BOF at IETF64\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: techspec-bounces@ietf.org The SOW will be aligned with the final version of draft-mankin-pub-req, whose text has been adjusted for this point in version 10. Brian Sam Hartman wrote: > I do not support Stewart's comment. > > However I will note that our current process requires the rfc-editor > to accept ASCII input along with non-normative PDF or PostScript > input. The SOW should reflect this current practice. > > _______________________________________________ Techspec mailing list Techspec@ietf.org https://www1.ietf.org/mailman/listinfo/techspec From techspec-bounces@ietf.org Thu Jul 13 16:06:52 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G17SP-0002sX-Ng; Thu, 13 Jul 2006 16:06:45 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G17SO-0002rr-FM; Thu, 13 Jul 2006 16:06:44 -0400 Received: from mtagate1.uk.ibm.com ([195.212.29.134]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G17SM-0005BQ-0r; Thu, 13 Jul 2006 16:06:44 -0400 Received: from d06nrmr1407.portsmouth.uk.ibm.com (d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185]) by mtagate1.uk.ibm.com (8.13.6/8.13.6) with ESMTP id k6DK6eYS194838 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 13 Jul 2006 20:06:41 GMT Received: from d06av04.portsmouth.uk.ibm.com (d06av04.portsmouth.uk.ibm.com [9.149.37.216]) by d06nrmr1407.portsmouth.uk.ibm.com (8.13.6/NCO/VER7.0) with ESMTP id k6DK8CKq131152 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 Jul 2006 21:08:12 +0100 Received: from d06av04.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av04.portsmouth.uk.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id k6DK6eb7026068; Thu, 13 Jul 2006 21:06:40 +0100 Received: from mail-gw3.hursley.ibm.com (mail-gw3.hursley.ibm.com [9.20.131.251]) by d06av04.portsmouth.uk.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k6DK6epn026065; Thu, 13 Jul 2006 21:06:40 +0100 Received: from [9.20.118.16] (helo=bf1v5-118.hursley.ibm.com) by mail-gw3.hursley.ibm.com with esmtp (Exim 4.50) id 1G17SJ-0003T3-RP; Thu, 13 Jul 2006 21:06:39 +0100 Received: from zurich.ibm.com (sig-9-145-248-133.de.ibm.com [9.145.248.133]) by bf1v5-118.hursley.ibm.com (AIX5.3/8.11.6p2/8.11.0) with SMTP id k6DK6c54010064; Thu, 13 Jul 2006 21:06:38 +0100 Message-ID: <44B6A7CD.5000106@zurich.ibm.com> Date: Thu, 13 Jul 2006 22:06:37 +0200 From: Brian E Carpenter Organization: IBM User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en, fr, de MIME-Version: 1.0 To: Stewart Bryant References: <44B2497D.3060000@isoc.org> <44B657C4.60102@cisco.com> <44B68D49.80505@zurich.ibm.com> <44B6950D.8090400@cisco.com> In-Reply-To: <44B6950D.8090400@cisco.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Cc: IAB , IETF Discussion , techspec@ietf.org, IAOC , The IESG , Sam Hartman Subject: [Techspec] Re: RFC Editor SOW Review X-BeenThere: techspec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion list for IETF Technical Specifications \(BOF at IETF64\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: techspec-bounces@ietf.org Stewart Bryant wrote: > Brian E Carpenter wrote: > >> The SOW will be aligned with the final version >> of draft-mankin-pub-req, whose text has been adjusted >> for this point in version 10. >> > I just greped v10 and there is no reference to pdf, nor to ps, > nor to RFC2223. Your grep missed "text, portable document format (pdf), etc.)" > > The text in section 3.9 in V10 seems ambiguous and should > align with RFC2223 - Instructions to RFC Authors It's meant to be wide enough to contain current practice but not limit us to current practice. Since RFC 2223 is very old and there are two drafts proposing to update it, we can't use it as a stable reference for generic requirements. Brian _______________________________________________ Techspec mailing list Techspec@ietf.org https://www1.ietf.org/mailman/listinfo/techspec From techspec-bounces@ietf.org Fri Jul 14 10:20:44 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G1OX4-0001mx-Cx; Fri, 14 Jul 2006 10:20:42 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G127y-0002Al-P1; Thu, 13 Jul 2006 10:25:18 -0400 Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G127x-0006Iu-Fb; Thu, 13 Jul 2006 10:25:18 -0400 Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 13 Jul 2006 16:25:18 +0200 Received: from [10.61.81.218] (ams3-vpn-dhcp4571.cisco.com [10.61.81.218]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k6DEPEUO011192; Thu, 13 Jul 2006 16:25:15 +0200 (MEST) Message-ID: <44B657C4.60102@cisco.com> Date: Thu, 13 Jul 2006 15:25:08 +0100 From: Stewart Bryant User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ray Pelletier References: <44B2497D.3060000@isoc.org> In-Reply-To: <44B2497D.3060000@isoc.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 X-Mailman-Approved-At: Fri, 14 Jul 2006 10:20:40 -0400 Cc: IAOC , IAB , IETF Discussion , techspec@ietf.org, The IESG Subject: [Techspec] Re: RFC Editor SOW Review X-BeenThere: techspec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion list for IETF Technical Specifications \(BOF at IETF64\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: techspec-bounces@ietf.org The SOW says: g. Document Format Conversions 1) Accept as input ascii text files and publish documents as ascii text files,postscript files, and pdf files 2) Accept supplemental source files that may contain information such as: code, formal descriptions (XML, ASN.1, etc.) graphics, data files, etc. 3) Publish documents as ascii text, postscript, and pdf files It is possible that the IETF will at some time in the future migrate to an input format other than ASCII text. Please can we amend the SOW to: a) Allow the IETF to experiment with the production of RFCs based on text formats other than ASCII text. b) Allow the IETF the ability to introduce at some time in the future an alternative input format to ASCII text if it so chooses. - Stewart _______________________________________________ Techspec mailing list Techspec@ietf.org https://www1.ietf.org/mailman/listinfo/techspec From techspec-bounces@ietf.org Fri Jul 14 10:20:49 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G1OX4-0001nQ-Jc; Fri, 14 Jul 2006 10:20:42 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G1ExV-0004uK-Pa; Fri, 14 Jul 2006 00:07:21 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G16Rp-0008KL-BF; Thu, 13 Jul 2006 15:02:05 -0400 Received: from ams-iport-1.cisco.com ([144.254.224.140]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G16D5-00048p-HP; Thu, 13 Jul 2006 14:46:53 -0400 Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 13 Jul 2006 20:46:50 +0200 Received: from [10.61.65.167] (ams3-vpn-dhcp423.cisco.com [10.61.65.167]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k6DIkhUO014176; Thu, 13 Jul 2006 20:46:48 +0200 (MEST) Message-ID: <44B6950D.8090400@cisco.com> Date: Thu, 13 Jul 2006 19:46:37 +0100 From: Stewart Bryant User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brian E Carpenter References: <44B2497D.3060000@isoc.org> <44B657C4.60102@cisco.com> <44B68D49.80505@zurich.ibm.com> In-Reply-To: <44B68D49.80505@zurich.ibm.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -2.6 (--) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad X-Mailman-Approved-At: Fri, 14 Jul 2006 10:20:40 -0400 Cc: IAB , IETF Discussion , techspec@ietf.org, IAOC , The IESG , Sam Hartman Subject: [Techspec] Re: RFC Editor SOW Review X-BeenThere: techspec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion list for IETF Technical Specifications \(BOF at IETF64\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: techspec-bounces@ietf.org Brian E Carpenter wrote: > The SOW will be aligned with the final version > of draft-mankin-pub-req, whose text has been adjusted > for this point in version 10. > I just greped v10 and there is no reference to pdf, nor to ps, nor to RFC2223. The text in section 3.9 in V10 seems ambiguous and should align with RFC2223 - Instructions to RFC Authors - Stewart _______________________________________________ Techspec mailing list Techspec@ietf.org https://www1.ietf.org/mailman/listinfo/techspec From techspec-bounces@ietf.org Fri Jul 14 10:20:49 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G1OX4-0001nB-Fv; Fri, 14 Jul 2006 10:20:42 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G12ol-0004sd-A7; Thu, 13 Jul 2006 11:09:31 -0400 Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G12bw-0007s1-OS; Thu, 13 Jul 2006 10:56:18 -0400 Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 13 Jul 2006 16:56:16 +0200 Received: from [10.61.81.218] (ams3-vpn-dhcp4571.cisco.com [10.61.81.218]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k6DEuEUO021708; Thu, 13 Jul 2006 16:56:14 +0200 (MEST) Message-ID: <44B65F08.2030901@cisco.com> Date: Thu, 13 Jul 2006 15:56:08 +0100 From: Stewart Bryant User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Stewart Bryant References: <44B2497D.3060000@isoc.org> <44B657C4.60102@cisco.com> In-Reply-To: <44B657C4.60102@cisco.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3 X-Mailman-Approved-At: Fri, 14 Jul 2006 10:20:40 -0400 Cc: IAB , IETF Discussion , techspec@ietf.org, IAOC , The IESG Subject: [Techspec] Re: RFC Editor SOW Review X-BeenThere: techspec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion list for IETF Technical Specifications \(BOF at IETF64\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: techspec-bounces@ietf.org Stewart Bryant wrote: > The SOW says: > > g. Document Format Conversions > 1) Accept as input ascii text files and publish documents as ascii text > files,postscript files, and pdf files > > 2) Accept supplemental source files that may contain information such > as: code, formal descriptions (XML, ASN.1, etc.) graphics, data files, > etc. > > 3) Publish documents as ascii text, postscript, and pdf files > > It is possible that the IETF will at some time in the future migrate > to an input format other than ASCII text. Please can we > amend the SOW to: > > a) Allow the IETF to experiment with the production of RFCs > based on text formats other than ASCII text. > > b) Allow the IETF the ability to introduce at some time in the > future an alternative input format to ASCII text if it so chooses. > > - Stewart Looking at the SOW again, it seems to completely ignore RFC2223.txt section 1 that says: "While the primary RFCs is always an ASCII text file, secondary or alternative versions of RFC may be provided in PostScript. This decision is motivated by the desire to include diagrams, drawings, and such in RFCs. PostScript documents (on paper only, so far) are visually more appealing and have better readability." and also Guidelines to Authors of Internet-Drafts section 2 that says: "PostScript and/or PDF are acceptable....." - Stewart > > > _______________________________________________ > Ietf mailing list > Ietf@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf > _______________________________________________ Techspec mailing list Techspec@ietf.org https://www1.ietf.org/mailman/listinfo/techspec From techspec-bounces@ietf.org Thu Jul 27 23:10:03 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G6Ijh-0000Hv-C6; Thu, 27 Jul 2006 23:10:01 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G6Ijg-00009J-57 for techspec@ietf.org; Thu, 27 Jul 2006 23:10:00 -0400 Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G6Ije-00029L-Sz for techspec@ietf.org; Thu, 27 Jul 2006 23:10:00 -0400 Received: from localhost ([127.0.0.1] helo=psg.com) by psg.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1G6Ije-000Jqt-Bp for techspec@ietf.org; Fri, 28 Jul 2006 03:09:58 +0000 To: techspec@ietf.org Date: Thu, 27 Jul 2006 20:09:58 -0700 From: Allison Mankin X-Spam-Score: 0.0 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 Subject: [Techspec] New requirement surfaced in RFP review - liaison X-BeenThere: techspec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mankin@psg.com List-Id: "Discussion list for IETF Technical Specifications \(BOF at IETF64\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: techspec-bounces@ietf.org Message-Id: During the RFP review, it was found that we missed reporting a requirement that is simply standard operating procedure, the liaison of the technical editor with the IESG. Since the RFP is meant to basically match draft-mankin-pub-req, we were requested to add this to our document for completeness. Here is the new requirement which will be going into version 11. Version 11 will also be resolving a few Discusses. Stephen will explain those small changes as he submits the update. 3.22 Liaison and Communication Task Description: It is very valuable for the technical publisher for an organization to have good information and communication about the work streams which will result in publication streams. In order to ensure a wide communication channel to the work, the technical publisher holds a liaison position on the IESG, where there can be valuable give-and-take about matters concerning the IETF standards stream. Derived Requirements: o Req-LIAISON-1 - Through a liaison participant, the technical publisher should take part in IESG formal meetings, IESG face-to-face activities at IETF, and other activities such as retreats. Allison _______________________________________________ Techspec mailing list Techspec@ietf.org https://www1.ietf.org/mailman/listinfo/techspec From techspec-bounces@ietf.org Fri Jul 28 19:08:46 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G6bRf-0000rF-Sh; Fri, 28 Jul 2006 19:08:39 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G6bRe-0000rA-ME for techspec@ietf.org; Fri, 28 Jul 2006 19:08:38 -0400 Received: from imr1.ericy.com ([198.24.6.9]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G6bRd-0001MQ-4O for techspec@ietf.org; Fri, 28 Jul 2006 19:08:38 -0400 Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se [138.85.77.51]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id k6SN7oNY012981 for ; Fri, 28 Jul 2006 18:08:36 -0500 Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.56]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 28 Jul 2006 18:08:35 -0500 Received: from eusrcmw720.eamcs.ericsson.se ([138.85.77.20]) by eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 28 Jul 2006 18:08:34 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 28 Jul 2006 18:08:31 -0500 Message-ID: <4DCBC973AF0D6E4FAF9CD998CE1C00380362729F@eusrcmw720.eamcs.ericsson.se> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: New Version Notification - draft-mankin-pub-req-11.txt Thread-Index: AcayfwiW9R0TDk8iRG+e1HOHzJMCmwAG0LkA From: "Stephen Hayes \(PL/EUS\)" To: X-OriginalArrivalTime: 28 Jul 2006 23:08:34.0950 (UTC) FILETIME=[C069BA60:01C6B29A] X-Spam-Score: 0.1 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Subject: [Techspec] FW: New Version Notification - draft-mankin-pub-req-11.txt X-BeenThere: techspec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion list for IETF Technical Specifications \(BOF at IETF64\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1069007972==" Errors-To: techspec-bounces@ietf.org --===============1069007972== Content-class: urn:content-classes:message Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 RllJLA0KDQpOZXcgdmVyc2lvbiBvZiBtYW5raW4tcHViLXJlcSBub3cgYXZhaWxhYmxlLiAgVGhp cyBhZGRyZXNzZXMgdGhlIHJlbWFpbmluZyBkaXNjdXNzIGNvbW1lbnRzIGFuZCB0aGUgYWRkaXRp b25hbCByZXF1aXJlbWVudCBtZW50aW9uZWQgcHJldmlvdXNseSBieSBBbGxpc29uLg0KDQpTdGVw aGVuDQoNCkNoYW5nZSBMb2c6DQptYW5raW4tcHViLXJlcS0xMCAtPiBtYW5raW4tcHViLXJlcS0x MQ0KDQoxLglTZWN0aW9uIDMuMSAocHJlLWFwcHJvdmFsIGVkaXRpbmcpIHdhcyB1cGRhdGVkIHRv IG1ha2UgaXQgY2xlYXJlciB0aGF0IGVhcmx5IGNvcHkgZWRpdGluZyBpcyBub3QgY3VycmVudGx5 IHBhcnQgb2YgdGhlIElFVEYgc3RhbmRhcmRzIHByb2Nlc3MgYW5kIHRoZSBJRVRGIG11c3Qgc3Rp bGwgbWFrZSBhIGRlY2lzaW9uIGFzIHRvIHdoZXRoZXIgaXQgd2lsbCBiZWNvbWUgcGFydCBvZiB0 aGUgcHJvY2Vzcy4NCg0KMi4JU2VjdGlvbnMgMi4xLCAzLjMsIGFuZCAzLjcgY2xlYW5lZCB1cCB0 aGUgd29yZGluZyB0byByZW1vdmUgdGhlIGFtYmlndWl0eSBhYm91dCB3aG8gdGhlIGRvY3VtZW50 IHNoZXBoZXJkIHdhcyBhbmQgd2hvIGhhZCB0aGUgYXV0aG9yaXR5IHRvIGFwcHJvdmUgY2hhbmdl cy4NCg0KMy4JQXMgQWxsaXNvbiBpbmRpY2F0ZWQgaW4gYSBwcmV2aW91cyBtYWlsOiBhIG5ldyBz ZWN0aW9uICgzLjIyKSBhbmQgcmVxdWlyZW1lbnQgd2FzIGFkZGVkIHRvIGNhcHR1cmUgdGhlIG5l ZWQgZm9yIGEgbGlhaXNvbiBmcm9tIHRoZSB0ZWNobmljYWwgcHVibGlzaGVyIHRvIHRoZSBJRVNH Lg0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBJRCBUcmFja2VyIFttYWls dG86aW50ZXJuZXQtZHJhZnRzLXJlcGx5QGlldGYub3JnXQ0KU2VudDogRnJpZGF5LCBKdWx5IDI4 LCAyMDA2IDI6NTAgUE0NClRvOiBtYW5raW5AcHNnLmNvbTsgU3RlcGhlbiBIYXllcyAoUEwvRVVT KTsgbGVzbGllQHRoaW5raW5nY2F0LmNvbTsNCmJyY0B6dXJpY2guaWJtLmNvbTsgbGlzYUBvc2Fm b3VuZGF0aW9uLm9yZzsgZmx1ZmZ5QGNpc2NvLmNvbQ0KU3ViamVjdDogTmV3IFZlcnNpb24gTm90 aWZpY2F0aW9uIC0gZHJhZnQtbWFua2luLXB1Yi1yZXEtMTEudHh0IA0KDQoNCk5ldyB2ZXJzaW9u ICgtMTEpIGhhcyBiZWVuIHN1Ym1pdHRlZCBmb3IgZHJhZnQtbWFua2luLXB1Yi1yZXEtMTEudHh0 Lg0KaHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtbWFua2luLXB1Yi1y ZXEtMTEudHh0DQoNCg0KDQpJRVRGIFNlY3JldGFyaWF0Lg0KDQo= --===============1069007972== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Techspec mailing list Techspec@ietf.org https://www1.ietf.org/mailman/listinfo/techspec --===============1069007972==-- From techspec-bounces@ietf.org Sun Jul 30 03:44:37 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G75yW-0008GV-I3; Sun, 30 Jul 2006 03:44:36 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G75yW-0008GQ-2A for techspec@ietf.org; Sun, 30 Jul 2006 03:44:36 -0400 Received: from smtp141.iad.emailsrvr.com ([207.97.245.141]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G75yU-0001xv-QY for techspec@ietf.org; Sun, 30 Jul 2006 03:44:36 -0400 Received: from zurich.ibm.com (d83-180-99-248.cust.tele2.ch [83.180.99.248]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: becarpenter@isoc.org) by relay4.r5.iad.mlsrvr.com (SMTP Server) with ESMTP id 01B2CC1F2; Sun, 30 Jul 2006 03:44:33 -0400 (EDT) Message-ID: <44CC6364.5020103@zurich.ibm.com> Date: Sun, 30 Jul 2006 09:44:36 +0200 From: Brian E Carpenter Organization: IBM User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en, fr, de MIME-Version: 1.0 To: "Stephen Hayes (PL/EUS)" Subject: Re: [Techspec] FW: New Version Notification - draft-mankin-pub-req-11.txt References: <4DCBC973AF0D6E4FAF9CD998CE1C00380362729F@eusrcmw720.eamcs.ericsson.se> In-Reply-To: <4DCBC973AF0D6E4FAF9CD998CE1C00380362729F@eusrcmw720.eamcs.ericsson.se> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: OK X-Spam-Score: 0.1 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Cc: techspec@ietf.org X-BeenThere: techspec@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion list for IETF Technical Specifications \(BOF at IETF64\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: techspec-bounces@ietf.org I'm glad to tell you that the remaining IESG DISCUSS ballots have been cleared, this document is good to go. Thanks everybody, this has been a very productive discussion. Brian Stephen Hayes (PL/EUS) wrote: > FYI, > > New version of mankin-pub-req now available. This addresses the remaining discuss comments and the additional requirement mentioned previously by Allison. > > Stephen > > Change Log: > mankin-pub-req-10 -> mankin-pub-req-11 > > 1. Section 3.1 (pre-approval editing) was updated to make it clearer that early copy editing is not currently part of the IETF standards process and the IETF must still make a decision as to whether it will become part of the process. > > 2. Sections 2.1, 3.3, and 3.7 cleaned up the wording to remove the ambiguity about who the document shepherd was and who had the authority to approve changes. > > 3. As Allison indicated in a previous mail: a new section (3.22) and requirement was added to capture the need for a liaison from the technical publisher to the IESG. > > > -----Original Message----- > From: ID Tracker [mailto:internet-drafts-reply@ietf.org] > Sent: Friday, July 28, 2006 2:50 PM > To: mankin@psg.com; Stephen Hayes (PL/EUS); leslie@thinkingcat.com; > brc@zurich.ibm.com; lisa@osafoundation.org; fluffy@cisco.com > Subject: New Version Notification - draft-mankin-pub-req-11.txt > > > New version (-11) has been submitted for draft-mankin-pub-req-11.txt. > http://www.ietf.org/internet-drafts/draft-mankin-pub-req-11.txt > > > > IETF Secretariat. > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Techspec mailing list > Techspec@ietf.org > https://www1.ietf.org/mailman/listinfo/techspec _______________________________________________ Techspec mailing list Techspec@ietf.org https://www1.ietf.org/mailman/listinfo/techspec