[Techspec] New requirement surfaced in RFP review - liaison

Allison Mankin <mankin@psg.com> Fri, 28 July 2006 03:10 UTC

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 <mankin@psg.com>) 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 <mankin@psg.com>
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\)" <techspec.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/techspec>, <mailto:techspec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/techspec>
List-Post: <mailto:techspec@ietf.org>
List-Help: <mailto:techspec-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/techspec>, <mailto:techspec-request@ietf.org?subject=subscribe>
Errors-To: techspec-bounces@ietf.org
Message-Id: <E1G6Ijh-0000Hv-C6@megatron.ietf.org>

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