From ops-area-bounces@ietf.org Wed Sep 05 06:07:25 2007
Return-path: <ops-area-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ISrn4-0004Cg-C4; Wed, 05 Sep 2007 06:07:18 -0400
Received: from ops-area by megatron.ietf.org with local (Exim 4.43)
	id 1ISrn3-000488-2M for ops-area-confirm+ok@megatron.ietf.org;
	Wed, 05 Sep 2007 06:07:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ISrn0-000430-Ne
	for ops-area@ietf.org; Wed, 05 Sep 2007 06:07:16 -0400
Received: from de307622-de-outbound.net.avaya.com ([198.152.71.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ISrmy-0006Zh-RG
	for ops-area@ietf.org; Wed, 05 Sep 2007 06:07:14 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by de307622-de-outbound.net.avaya.com with ESMTP;
	05 Sep 2007 06:07:12 -0400
X-IronPort-AV: i="4.20,210,1186372800"; 
	d="scan'208"; a="54899431:sNHT13804014"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 5 Sep 2007 12:06:31 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A043C3D19@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Vancouver BOF and WG requests
Thread-Index: AcfvkeEdx9J/TcLgRqi2p7fELV4n9wAEhjaQ
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5ba9b8496764663b12c333825fbf6b3d
Subject: [OPS-AREA] Vancouver BOF and WG requests
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Errors-To: ops-area-bounces@ietf.org

=20


Please note the following deadlines:

> -----------------------------------------------------------------
> 70th IETF - Vancouver, BC, Canada
> Meeting Dates: December 2-7, 2007
> -----------------------------------------------------------------
> We will be accepting scheduling requests for all Working Groups and=20
> BOFs starting today, Tuesday, September 4, 2007.  The milestones and=20
> deadlines for scheduling-related activities are as follows:
>
> -- Cut-off date for requests to schedule Working Group meetings and=20
> for preliminary BOF proposals to ADs: Monday, October 1 at 17:00 ET=20
> (21:00 UTC/GMT).
> -- Cut-off date for requests to schedule BoFs: Monday, October 22 at=20
> 17:00 ET (21:00 UTC/GMT).
> -- Preliminary agenda published for comment: Friday, October 26 by=20
> midnight ET.
> -- Cut-off date for requests to reschedule Working Group and BOF
meetings:
> Wednesday, November 7 at 09:00 ET (14:00 UTC/GMT).
> -- Final agenda published: Monday, November 12 before midnight ET.
> -- Draft Working Group agendas due: Wednesday, November 21 at 17:00 ET

> (22:00 UTC/GMT).
> -- Revised Working Group agendas due: Monday, November 26 at 12:00 ET=20
> (17:00 UTC/GMT), upload using IETF Meeting Materials Management Tool
>
> Submitting Requests for Working Group and BOF Sessions
>
> Please submit requests to schedule your Working Group sessions using=20
> the "IETF Meeting Session Request Tool," a Web-based tool for=20
> submitting all of the information that the Secretariat requires to=20
> schedule your sessions.
>
> The URL for the tool is:
>
> https://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi
>
> Instructions for using the tool are available at:
>
> http://www.ietf.org/instructions/session_request_tool_instruction.html
>
> Please send requests to schedule your BOF sessions to agenda@ietf.org.

> Please include the acronym of your BOF in the subject line of the=20
> message, and include all of the information specified in item (4) of=20
> "Requesting Meeting Sessions at IETF Meetings" in the body.  (This=20
> document is included below.)
>
> Submitting Session Agendas
>
> For the convenience of meeting attendees, we ask that you submit the=20
> agendas for your Working Group sessions as early as possible.  Draft=20
> Working Group agendas are due Wednesday, November 21 by 17:00 ET=20
> (22:00 UTC/GMT).  Revised Working Group agendas are due no later than=20
> Monday, November 26 at 12:00 ET (17:00 UTC/GMT).  The proposed agenda=20
> for a BOF session should be submitted along with your request for a=20
> session.  Please be sure to copy your Area Director on that message.
>
> Please submit the agendas for your Working Group sessions using the=20
> "IETF Meeting Materials Management Tool," a Web-based tool for making=20
> your meeting agenda, minutes, and presentation slides available to the

> community before, during, and after an IETF meeting.  If you are a BOF

> chair, then you may use the tool to submit a revised agenda as well as

> other materials for your BOF once the BOF has been approved.
>
> The URL for the tool is:
>
> https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi
>
> Additional information about this tool is available at:
>
> http://www.ietf.org/instructions/meeting_materials_tool.html
>
> Agendas submitted via the tool will be available to the public on the=20
> "IETF Meeting Materials" Web page as soon as they are submitted.
>
> The URL for the "IETF 70 Meeting Materials" Web page is:
>
> =
https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=3D
> 70
>
> If you are a Working Group chair, then you already have accounts on=20
> the "IETF Meeting Session Request Tool" and the "IETF Meeting=20
> Materials Management Tool."  The same User ID and password will work
for both tools.
>   If you are a BOF chair who is not also a Working Group chair, then=20
> you will be given an account on the "IETF Meeting Materials Management
Tool"
> when your BOF has been approved.  If you require assistance in using=20
> either tool, or wish to report a bug, then please send a message to:
> ietf-action@ietf.org.
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> For your convenience, comprehensive information on requesting meeting=20
> sessions at IETF 70 is presented below:
>
> 1. Requests to schedule Working Group sessions should be submitted=20
> using the "IETF Meeting Session Request Tool," a Web-based tool for=20
> submitting all of the information required by the Secretariat to=20
> schedule your sessions.  The URL for the tool is:
>
> https://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi
>
> Instructions for using the tool are available at:
>
> http://www.ietf.org/instructions/session_request_tool_instruction.html
>
> If you require an account on this tool, or assistance in using it,=20
> then please send a message to ietf-action@ietf.org.  If you are unable

> to use the tool, then you may send your request via e-mail to=20
> agenda@ietf.org, with a copy to the appropriate Area Director(s).
>
> Requests to schedule BOF sessions must be sent to agenda@ietf.org with

> a copy to the appropriate Area Director(s).
>
> When submitting a Working Group or BOF session request by e-mail,=20
> please include the Working Group or BOF acronym in the Subject line.
>
> 2. BOFs will NOT be scheduled unless the Area Director(s) approved=20
> request is accompanied by a BOF'S FULL NAME AND ACRONYM, AREA,=20
> CHAIR(S)
> NAME(S) (given together with e-mail address(es)), AN AGENDA AND FULL=20
> DESCRIPTION, and the information requested in (4) below. (Please read=20
> the BOF Procedure at: http://www.ietf.org/ietf/1bof-procedures.txt=20
> before requesting a session for a BOF.)
>
> 3. A Working Group may request either one or two sessions.  If your=20
> Working Group requires more than two sessions, then your request must=20
> be approved by an Area Director.  Additional sessions will be=20
> assigned, based on availability, after Wednesday, November 7 at 09:00=20
> ET (14:00 UTC/GMT), the cut-off date for requests to reschedule a
session.
>
> 4. You MUST provide the following information before a Working Group=20
> or BOF session will be scheduled:
>
>     a. Working Group or BOF full name with acronym in brackets:=20
>
>     b. AREA under which Working Group or BOF appears:
>
>     c. CONFLICTS you wish to avoid, please be as specific as possible:
>
>     d. Expected Attendance (figures from the 69th IETF meeting are=20
> included at the end of this message):
>
>     e. Special requests:
>
>     f. Number of sessions:
>
>     g. Length of session:=20
>        - 1 hour=20
>        - 2 hours=20
>        - 2 1/2 hours
>
> For more information on scheduling Working Group and BOF sessions,=20
> please refer to RFC 2418 (BCP 25), "IETF Working Group Guidelines and
Procedures"
> (http://www.ietf.org/rfc/rfc2418.txt).
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> For your convenience please find here a list of the IETF Area=20
> Directors with their e-mail addresses:
>
> IETF Chair
> Russ Housley <housley@vigilsec.com>
>
> Applications Area (app)
> Lisa Dusseault <lisa@osafoundation.org> Chris Newman=20
> <chris.newman@sun.com>
>
> Internet Area (int)
> Jari Arkko <jari.arkko@piuha.net>
> Mark Townsley <townsley@cisco.com>
>
> Operations & Management Area (ops)
> Ronald Bonica <rbonica@juniper.net>
> Dan Romascanu <dromasca@avaya.com>
>
> Real-time Applications and Infrastructure Area (rai) Cullen Jennings=20
> <fluffy@cisco.com> Jon Peterson <jon.peterson@neustar.biz>
>
> Routing Area (rtg)
> Ross Callon <rcallon@juniper.net>
> David Ward <dward@cisco.com>
>
> Security Area (sec)
> Sam Hartman <hartmans-ietf@mit.edu>
> William Polk <wpolk@nist.gov>
>
> Transport Area (tsv)
> Lars Eggert <eggert@nokia.com>
> Magnus Westerlund <magnus.westerlund@ericsson.com>=20
> =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
> 69th IETF Meeting Attendance Number
>
> 16ng	66
> 6lowpan	No Blue Sheets
> ancp	No Blue Sheets
> apm (BoF)	93
> apparea (AG)	75
> autoconf	77
> autoconf (2nd session)	63
> avt	94
> avt (2nd session)	73
> behave	53
> biff (BoF)	30
> bliss	123
> bmwg	38
> btns	38
> calcify	14
> capwap	44
> ccamp	112
> ccamp (2nd session)	95
> dccp	33
> dhc	66
> dime	35
> dkim	58
> dnsop	104
> dtnrg	51
> eai	47
> ecrit	93
> emu	39
> enum	82
> forces	17
> geopriv	100
> grow	73
> hiprg/emerg	77
> hokey	87
> httpbis (BoF)	61
> iccrg	52
> idr	112
> intarea (AG)	120
> ipdvb	7
> ipfix	24
> ippm	No Blue Sheets
> ipr	23
> isis	58
> isms	25
> keyprov 	46
> kitten	17
> krb-wg	32
> krb-wg (2nd session)	21
> l1vpn	CANCELLED
> l2vpn	No Blue Sheets
> l3vpn	83
> lemonade	35
> lemonade (2nd session)	25
> ltans	16
> manet	77
> mboned	50
> mediactrl	42
> mip4	31
> mip6	101
> mipshop	100
> mmusic	42
> mmusic (2nd session)	77
> mobopts (RG)	85
> monami6	90
> mpls	152
> nea	62
> nee (BoF)	46
> nemo	92
> netconf	38
> netlmm	99
> nfsv4	20
> nsis	36
> ntp	37
> opsawg	66
> ospf	56
> p2psip (adhoc)	36
> p2psip	154
> pana	34
> pce	63
> pcn	79
> pim	32
> pkix	52
> pwe3	127
> radext	39
> rmt	32
> rpsec	50
> rrg	145
> rtgarea (AG)	136
> rtgwg	97
> saag (AG)	149
> samrg	41
> sasl	31
> sidr	89
> sieve	17
> simple	81
> sip 	162
> sip (2nd session)	128
> sipping	137
> sipping (2nd session)	135
> smime	17
> softwire	51
> speermint	125
> tam (BoF)	103
> tcpm	35
> tls	54
> trill	44
> trill (2nd session)	27
> tsvarea (AG)	67
> tsvwg	81
> v6ops	130
> vcarddav (BoF)	24
> xcon	45
> xsdmi (BoF)	29
>


_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-area



From ops-area-bounces@ietf.org Mon Sep 10 05:41:25 2007
Return-path: <ops-area-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IUflh-0003nr-Sc; Mon, 10 Sep 2007 05:41:21 -0400
Received: from ops-area by megatron.ietf.org with local (Exim 4.43)
	id 1IUflf-0003ng-Qp for ops-area-confirm+ok@megatron.ietf.org;
	Mon, 10 Sep 2007 05:41:20 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IUflO-0003fH-OE; Mon, 10 Sep 2007 05:41:02 -0400
Received: from co300216-co-outbound.net.avaya.com ([198.152.13.100]
	helo=co300216-co-outbound.avaya.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IUflN-0007Qy-Cs; Mon, 10 Sep 2007 05:41:02 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.14])
	by co300216-co-outbound.avaya.com with ESMTP; 10 Sep 2007 05:40:59 -0400
X-IronPort-AV: i="4.20,230,1186372800"; 
	d="scan'208"; a="63529889:sNHT11904390"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 10 Sep 2007 11:40:18 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A043F65F5@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Nomcom 2007-8: Nominations Close on Sep 10, 2007
Thread-Index: AcfxiKR8sE/GsVAeQU229Ct7pUHUaACBYKWQ
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <mib-doctors@ietf.org>, <ops-area@ietf.org>, <dns-dir@ops.ietf.org>,
	<ngo@ietf.org>, <mib2rdml@ietf.org>, <meta-model@ietf.org>,
	<aaa-doctors@ietf.org>, "Ops-Nm" <ops-nm@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: 
Subject: [OPS-AREA] FW: Nomcom 2007-8: Nominations Close on Sep 10, 2007
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Errors-To: ops-area-bounces@ietf.org

=20
Please see the message below from the NomCom chair.=20

Dan


=20

-----Original Message-----
From: Lakshminath Dondeti [mailto:ldondeti@qualcomm.com]=20
Sent: Friday, September 07, 2007 10:53 PM
To: ietf-announce@ietf.org; wgchairs@ietf.org; IESG IESG; IAB IAB
Subject: Nomcom 2007-8: Nominations Close on Sep 10, 2007

WGchairs, IESG and IAB members

Please forward this request to the lists you manage and request feedback
and nominations.

All,

Here is the link to nominate:=20
https://tools.ietf.org/group/nomcom/07/nominate

You may also send nominations or comments via email to nomcom07@ietf.org
or ldondeti@qualcomm.com.

We have received very few nominations (1, 2, 2, 2, 3, 4, 8, 8, 19) and
even fewer accepted (1-2 people in each area, IAB acceptances is 4 at
last count).

I request the community to provide feedback on the incumbents (send
email or send notes via the web page).

1) If you think that the incumbent is doing a good job
     a) provide feedback AND
     b) nominate similar people just in case there is strong negative
feedback on the incumbent

2) If you think the incumbent can do somethings better
    a) provide feedback AND
    b) nominate someone who you think might do better

Candidates, if time commitment is the only issue, please indicate that
to the nomcom and accept the nominations.

thanks,
Lakshminath


_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-area



From ops-area-bounces@ietf.org Tue Sep 11 10:13:25 2007
Return-path: <ops-area-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IV6UT-0003NW-9a; Tue, 11 Sep 2007 10:13:21 -0400
Received: from ops-area by megatron.ietf.org with local (Exim 4.43)
	id 1IV6UR-0003If-Ph for ops-area-confirm+ok@megatron.ietf.org;
	Tue, 11 Sep 2007 10:13:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IV6UO-0003B0-95; Tue, 11 Sep 2007 10:13:16 -0400
Received: from nj300815-nj-outbound.net.avaya.com ([198.152.12.100]
	helo=nj300815-nj-outbound.avaya.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1IV6UM-0003tz-LP; Tue, 11 Sep 2007 10:13:15 -0400
Received: from 14.140.8.135.in-addr.arpa (HELO 307622ANEX5.global.avaya.com)
	([135.64.140.14])
	by nj300815-nj-outbound.avaya.com with ESMTP; 11 Sep 2007 10:13:11 -0400
X-IronPort-AV: i="4.20,238,1186372800"; 
	d="scan'208"; a="60399146:sNHT12287376"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 11 Sep 2007 16:12:58 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A043F6B64@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Nomcom 2007-8: Nominations Deadline Extended to Sep 17, 2007
Thread-Index: Acf0N4aTkP6ahAgSRsq1eP/2+Xqo0QARhN0A
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>, <mib-doctors@ietf.org>, <aaa-doctors@ietf.org>,
	<ngo@ietf.org>, <mib2rdml@ietf.org>, <meta-model@ietf.org>,
	<opsawg@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: 
Subject: [OPS-AREA] FW: Nomcom 2007-8: Nominations Deadline Extended to Sep
	17, 2007
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Errors-To: ops-area-bounces@ietf.org

=20


=20

-----Original Message-----
From: Lakshminath Dondeti [mailto:ldondeti@qualcomm.com]=20
Sent: Tuesday, September 11, 2007 8:48 AM
To: ietf-announce@ietf.org
Cc: wgchairs@ietf.org
Subject: Nomcom 2007-8: Nominations Deadline Extended to Sep 17, 2007

Folks,

Many of you responded well to the reminder calls for nominations sent
recently.  There was also an up-tick in the nominations acceptances as
well (in some cases).  The nomcom appreciates the community's response
very much.

However, we are still short in a few areas; at the moment, we have the
following numbers of nominations: 3 4 4 6 6 10 12 21 44 (some of these
folks have already rejected the nominations; I haven't had the time to
update the numbers yet).

The numbers on acceptances are still *very* low; in 3 (or may be 4)
areas, we have only ONE candidate so far.

In the discussions on this topic, it was argued that folks may be still
returning from their summer vacations.  Some candidates have hinted that
it may take some more time to get the necessary approvals.  Keeping
those considerations in mind, I am extending the nominations deadline to
Sep 17, 2007 AOE.  Candidates are requested to consider the chance to
serve the IETF and accept the nominations.  The questionnaires are now
due Sep 24, 2007 AOE.

Here is the link to nominate:=20
https://tools.ietf.org/group/nomcom/07/nominate
You may also send nominations or comments via email to nomcom07@ietf.org
or ldondeti@qualcomm.com.

thanks,
Lakshminath


_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-area



From ops-area-bounces@ietf.org Sun Sep 16 06:21:02 2007
Return-path: <ops-area-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IWrFE-0006mX-0d; Sun, 16 Sep 2007 06:20:52 -0400
Received: from ops-area by megatron.ietf.org with local (Exim 4.43)
	id 1IWrFC-0006mQ-6F for ops-area-confirm+ok@megatron.ietf.org;
	Sun, 16 Sep 2007 06:20:50 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IWrFB-0006mI-SE
	for ops-area@ietf.org; Sun, 16 Sep 2007 06:20:49 -0400
Received: from co300216-co-outbound.net.avaya.com ([198.152.13.100]
	helo=co300216-co-outbound.avaya.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IWrFB-0005Hb-IS
	for ops-area@ietf.org; Sun, 16 Sep 2007 06:20:49 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16])
	by co300216-co-outbound.avaya.com with ESMTP; 16 Sep 2007 06:20:48 -0400
X-IronPort-AV: i="4.20,260,1186372800"; 
	d="scan'208"; a="65733459:sNHT11261922"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Sun, 16 Sep 2007 12:20:07 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A043F70DA@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Management Issue: Formation of RAI Review Team
Thread-Index: Acf3J6wbh3Vp8UixSZSlcAmpcJHB2gBI2O5g
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Subject: [OPS-AREA] FW: Management Issue: Formation of RAI Review Team
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Errors-To: ops-area-bounces@ietf.org

=20


=20

-----Original Message-----
From: Cullen Jennings [mailto:fluffy@cisco.com]=20
Sent: Saturday, September 15, 2007 2:31 AM
To: IESG IESG
Subject: Management Issue: Formation of RAI Review Team


The RAI area is planning on forming a Review team. This team is
primarily to give the chairs in RAI a resource to use if they want to
get RAI documents reviewed around the time they are get adopted as a WG
items - there's no need to use it if the chair does not want to. =20
It could also get used a resource other times when some RAI review needs
to happen on some specific document but that would be a far less common
- it is not meant to review all documents like Sec Review or Gen Art.
Mary Barnes will run it.

FAQ - http://www.softarmor.com/rai/art/FAQ.html

Guidelines - http://www.softarmor.com/rai/art/review-guidelines.html

Initial team list - http://www.softarmor.com/rai/art/rai-reviewer-
list.html


_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-area



From ops-area-bounces@ietf.org Tue Sep 18 10:54:51 2007
Return-path: <ops-area-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IXeR6-0001ci-4m; Tue, 18 Sep 2007 10:52:24 -0400
Received: from ops-area by megatron.ietf.org with local (Exim 4.43)
	id 1IXeR5-0001cZ-0t for ops-area-confirm+ok@megatron.ietf.org;
	Tue, 18 Sep 2007 10:52:23 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IXeR4-0001an-Kk
	for ops-area@ietf.org; Tue, 18 Sep 2007 10:52:22 -0400
Received: from co300216-co-outbound.net.avaya.com ([198.152.13.100]
	helo=co300216-co-outbound.avaya.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IXeR3-0004w7-Uw
	for ops-area@ietf.org; Tue, 18 Sep 2007 10:52:22 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16])
	by co300216-co-outbound.avaya.com with ESMTP; 18 Sep 2007 10:52:20 -0400
X-IronPort-AV: i="4.20,269,1186372800"; d="txt'?scan'208,217";
	a="66416965:sNHT19312020"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C7FA03.6BAEEAB9"
Date: Tue, 18 Sep 2007 16:51:39 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0442ECED@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: [New-work] OMA New Work - 1 Work Item Approved - XDM and
	PresenceGuidelines
Thread-Index: Acf1IKWUdzzn9WSoT/ea/tSqy+xV7wE4rVwA
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cdb443e3957ca9b4c5b55e78cfcf4b26
Subject: [OPS-AREA] FW: [New-work] OMA New Work - 1 Work Item Approved - XDM
	and PresenceGuidelines
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Errors-To: ops-area-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7FA03.6BAEEAB9
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_002_01C7FA03.6BAEEAB9"


------_=_NextPart_002_01C7FA03.6BAEEAB9
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20
=20
=20
=20

________________________________

From: Victoria Gray [mailto:Victoria.Gray@forapolis.com]=20
Sent: Wednesday, September 12, 2007 12:38 PM
To: new-work@ietf.org
Subject: [New-work] OMA New Work - 1 Work Item Approved - XDM and
PresenceGuidelines


Dear All,

OMA would like to inform all the organisations subscribed to the IETF
new-work list of the approval of 1 work item:

1 XDM (XML Document Management) and Presence Guidelines WI:

http://www.openmobilealliance.org/ftp/Public_documents/TP/Permanent_docu
ments/OMA-WID_0156-XDM_PRS_IMPL-V1_0-20070911-A.zip
<http://www.openmobilealliance.org/ftp/Public_documents/TP/Permanent_doc
uments/OMA-WID_0156-XDM_PRS_IMPL-V1_0-20070911-A.zip>=20

The purpose of XDM and PRS Implementation Guideline Work Item is to
provide guidelines to designers for the implementation of the XDM and
Presence SIMPLE Enablers.

The work item will focus on describing common practices, valuable design
choices and real life examples of particular features. The benefits of
implementation guidelines include smooth migration between devices and
enabler releases and improved performance of the service.=20

This work item has been allocated to the OMA PAG (Presence and
Availability WG) for development.

Best regards,

Victoria Gray on behalf of OMA.

=20
Victoria Gray
FORApolis / DSO
Tel +33 (0)4 92 94 49 23
Fax +33 (0)4 92 38 49 23
GSM +33 (0)6 73 99 62 90
victoria.gray@forapolis.com
=20
MSN: victoria.gray@forapolis.com <mailto:victoria.gray@forapolis.com>
Yahoo!: bluevicci
Skype: victoria-gray  Google: vics.gray@gmail.com
=20

------_=_NextPart_002_01C7FA03.6BAEEAB9
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns:o =3D "urn:schemas-microsoft-com:office:office"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.3157" name=3DGENERATOR></HEAD>
<BODY>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Victoria Gray=20
[mailto:Victoria.Gray@forapolis.com] <BR><B>Sent:</B> Wednesday, =
September 12,=20
2007 12:38 PM<BR><B>To:</B> new-work@ietf.org<BR><B>Subject:</B> =
[New-work] OMA=20
New Work - 1 Work Item Approved - XDM and=20
PresenceGuidelines<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><FONT size=3D2>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial>Dear All,</FONT></DIV>
<DIV>
<P><FONT face=3DArial>OMA would like to inform all the organisations =
subscribed to=20
the IETF new-work list of the approval of&nbsp;<SPAN=20
class=3D901220807-20072005>1</SPAN>&nbsp;work item:</FONT></P>
<P><FONT face=3DArial><SPAN class=3D341403907-27072005>1&nbsp;<SPAN=20
class=3D365382809-12092007>XDM (XML Document Management) and Presence=20
Guidelines</SPAN>&nbsp;</SPAN><SPAN=20
class=3D901220807-20072005>WI</SPAN>:</FONT></P><SPAN=20
class=3D351522609-13072005><FONT size=3D1><FONT size=3D2><SPAN=20
class=3D341403907-27072005><SPAN class=3D400565108-27072005><FONT =
size=3D2>
<P></FONT><A=20
href=3D"http://www.openmobilealliance.org/ftp/Public_documents/TP/Permane=
nt_documents/OMA-WID_0156-XDM_PRS_IMPL-V1_0-20070911-A.zip"><U><FONT=20
size=3D2><FONT face=3DArial=20
color=3D#000000>http://www.openmobilealliance.org/ftp/Public_documents/TP=
/Permanent_documents/OMA-WID_0156-XDM_PRS_IMPL-V1_0-20070911-A.zip</FONT>=
</U></FONT></A></P></SPAN></SPAN></FONT></FONT></SPAN><SPAN=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial; mso-bidi-font-size: 10.0pt; =
mso-bidi-font-family: 'Times New Roman'; mso-fareast-language: KO; =
mso-bidi-font-weight: bold"><SPAN=20
style=3D"FONT-FAMILY: Arial; mso-bidi-font-family: 'Times New Roman'; =
mso-bidi-font-weight: bold">
<P class=3DMsoNormal style=3D"MARGIN: 6pt 0cm 0pt"><SPAN=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial; mso-bidi-font-size: 10.0pt; =
mso-bidi-font-family: 'Times New Roman'; mso-bidi-font-weight: =
bold"><FONT=20
size=3D2>The purpose of XDM and PRS Implementation Guideline Work Item =
is to=20
provide guidelines to designers for the implementation of the XDM and =
Presence=20
SIMPLE Enablers.<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal style=3D"MARGIN: 6pt 0cm 0pt"><SPAN=20
style=3D"FONT-SIZE: 9pt; FONT-FAMILY: Arial; mso-bidi-font-size: 10.0pt; =
mso-bidi-font-family: 'Times New Roman'; mso-bidi-font-weight: =
bold"><FONT=20
size=3D2>The work item will focus on describing common practices, =
valuable design=20
choices and real life examples of particular features. The benefits of=20
implementation guidelines include smooth migration between devices and =
enabler=20
releases and improved performance of the service. =
<o:p></o:p></FONT></SPAN></P>
<P class=3DMsoNormal=20
style=3D"TEXT-JUSTIFY: inter-ideograph; MARGIN: 6pt 0cm 0pt; TEXT-ALIGN: =
justify; mso-margin-top-alt: auto; mso-margin-bottom-alt: =
auto"></SPAN></SPAN><FONT=20
face=3DArial><SPAN class=3D901220807-20072005>T</SPAN>h<SPAN=20
class=3D901220807-20072005>i</SPAN>s work item ha<SPAN=20
class=3D901220807-20072005>s</SPAN> been<SPAN =
class=3D901220807-20072005>=20
</SPAN>allocated to the OMA&nbsp;<SPAN =
class=3D365382809-12092007>PAG</SPAN><SPAN=20
class=3D901220807-20072005><SPAN class=3D341403907-27072005> =
</SPAN></SPAN>(<SPAN=20
class=3D901220807-20072005><SPAN class=3D341403907-27072005><SPAN=20
class=3D365382809-12092007>Presence and Availability =
</SPAN>WG</SPAN></SPAN>)=20
for<SPAN class=3D341403907-27072005>&nbsp;</SPAN><SPAN=20
class=3D901220807-20072005>development</SPAN>.</FONT></P>
<P><FONT face=3DArial>Best regards,</FONT></P>
<P><FONT face=3DArial>Victoria Gray on behalf of=20
OMA.</FONT></P></DIV></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV align=3Dleft>
<DIV align=3Dcenter><FONT face=3DTahoma size=3D1><STRONG>Victoria=20
Gray</STRONG></FONT></DIV>
<DIV align=3Dcenter><FONT face=3DTahoma size=3D1>FORApolis / =
DSO</FONT></DIV>
<DIV align=3Dcenter><FONT face=3DTahoma size=3D1>Tel +33 (0)4 92 94 49 =
23</FONT></DIV>
<DIV align=3Dcenter><FONT face=3DTahoma size=3D1>Fax +33 (0)4 92 38 49 =
23</FONT></DIV>
<DIV align=3Dcenter><FONT face=3DTahoma size=3D1>GSM +33 (0)6 73 99 62 =
90</FONT></DIV>
<DIV align=3Dcenter><FONT face=3DTahoma size=3D1><A=20
title=3Dmailto:victoria.gray@forapolis.com=20
href=3D"mailto:victoria.gray@forapolis.com">victoria.gray@forapolis.com</=
A></FONT></DIV>
<DIV align=3Dcenter><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV align=3Dcenter><FONT face=3DTahoma size=3D1>MSN: </FONT><A=20
href=3D"mailto:victoria.gray@forapolis.com"><FONT face=3DTahoma=20
size=3D1><STRONG>victoria.gray@forapolis.com</STRONG></FONT></A><FONT =
size=3D1><FONT=20
face=3DTahoma>&nbsp;&nbsp; Yahoo!: <STRONG><FONT=20
color=3D#0000ff>bluevicci</FONT></STRONG></FONT></FONT></DIV>
<DIV align=3Dcenter><FONT size=3D1><FONT face=3DTahoma>Skype: =
<STRONG><FONT=20
color=3D#0000ff>victoria-gray</FONT></STRONG>&nbsp; Google: =
<STRONG><FONT=20
color=3D#0000ff><A=20
href=3D"mailto:vics.gray@gmail.com">vics.gray@gmail.com</A></FONT></STRON=
G></FONT></FONT></DIV></DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

------_=_NextPart_002_01C7FA03.6BAEEAB9--

------_=_NextPart_001_01C7FA03.6BAEEAB9
Content-Type: text/plain;
	name="ATT44326.txt"
Content-Transfer-Encoding: base64
Content-Description: ATT44326.txt
Content-Disposition: inline;
	filename="ATT44326.txt"

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCk5ldy13b3Jr
IG1haWxpbmcgbGlzdA0KTmV3LXdvcmtAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3MS5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL25ldy13b3JrDQo=

------_=_NextPart_001_01C7FA03.6BAEEAB9
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-area

------_=_NextPart_001_01C7FA03.6BAEEAB9--





From ops-area-bounces@ietf.org Thu Sep 20 03:34:17 2007
Return-path: <ops-area-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYGUM-0002Qu-4D; Thu, 20 Sep 2007 03:30:18 -0400
Received: from ops-area by megatron.ietf.org with local (Exim 4.43)
	id 1IYGUL-0002Qn-MI for ops-area-confirm+ok@megatron.ietf.org;
	Thu, 20 Sep 2007 03:30:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IYGUH-0002Pp-Bm
	for ops-area@ietf.org; Thu, 20 Sep 2007 03:30:13 -0400
Received: from co300216-co-outbound.net.avaya.com ([198.152.13.100]
	helo=co300216-co-outbound.avaya.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IYGUG-0004p7-41
	for ops-area@ietf.org; Thu, 20 Sep 2007 03:30:13 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16])
	by co300216-co-outbound.avaya.com with ESMTP; 20 Sep 2007 03:29:55 -0400
X-IronPort-AV: i="4.20,277,1186372800"; 
	d="scan'208"; a="67031729:sNHT11770146"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 20 Sep 2007 09:29:22 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0442F177@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Deployment of the Internet-Draft Submission Tool 
Thread-Index: Acf68+dWMQIbNFMgR92X1BeEftEYLwAZAqwg
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Subject: [OPS-AREA] FW: Deployment of the Internet-Draft Submission Tool 
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Errors-To: ops-area-bounces@ietf.org

=20


=20

-----Original Message-----
From: IETF Secretariat [mailto:ietf-secretariat@ietf.org]=20
Sent: Wednesday, September 19, 2007 9:32 PM
To: IETF Announcement list
Cc: wgchairs@ietf.org; iesg@ietf.org
Subject: Deployment of the Internet-Draft Submission Tool=20

The IETF Secretariat is pleased to announce the deployment of the
Internet-Draft Submission Tool (IDST)-Phase I.  The IDST is a Web-based
application that will allow an IETF participant to submit an
Internet-Draft online, obtain approval to post the draft (if necessary),
and make the draft immediately available to the community on the IETF
Web site without the assistance of the Secretariat (in most cases).

The URL for the IDST is:
https://datatracker.ietf.org/idst/upload.cgi

The URL for instructions for using the IDST is:
http://www.ietf.org/idsubmit_instructions.html

Although it will still be possible to submit your drafts by e-mail
(i.e., by sending them to internet-drafts@ietf.org), the tool is
available for use effective immediately, and we encourage you to submit
your drafts via the tool starting today.

If you have any questions about using the tool or wish to report a bug,
then please send a message to idst-developers@ietf.org.

Enjoy!!

The IETF Secretariat


_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-area



From ops-area-bounces@ietf.org Thu Sep 20 09:35:24 2007
Return-path: <ops-area-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYM8E-00035Y-Dx; Thu, 20 Sep 2007 09:31:50 -0400
Received: from ops-area by megatron.ietf.org with local (Exim 4.43)
	id 1IYM8D-00035O-Hq for ops-area-confirm+ok@megatron.ietf.org;
	Thu, 20 Sep 2007 09:31:49 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IYM8D-00035F-6G
	for ops-area@ietf.org; Thu, 20 Sep 2007 09:31:49 -0400
Received: from de307622-de-outbound.net.avaya.com ([198.152.71.100])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IYM87-0004ys-QG
	for ops-area@ietf.org; Thu, 20 Sep 2007 09:31:49 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16])
	by de307622-de-outbound.net.avaya.com with ESMTP;
	20 Sep 2007 09:31:25 -0400
X-IronPort-AV: i="4.20,278,1186372800"; d="scan'208"; a="59394884:sNHT7409850"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 20 Sep 2007 15:30:45 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0442F320@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: OPSAREA Open Meeting
Thread-Index: Acf7inKO19J+BmwTSt67YtCXAkMoHA==
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Subject: [OPS-AREA] OPSAREA Open Meeting
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Errors-To: ops-area-bounces@ietf.org

The Vancouver meeting is that other IETF meeting where the OPS Area will
be holding an open meeting. I have requested a two hours slot. Please
suggest agenda items for discussion in Vancouver. Those can include but
are not restricted to:=20

- mini-BOF sessions as we had in Prague
- operational and implementation reports
- discussions on current work in the area and proposals for new work

Time will be reserved for the open mic session.=20

Dan

PS - if this was not clear, this session is different from the OPSAWG
which I expect to meet separately to discuss items on their charter and
other work candidate for OPSAWG.=20



=20


_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-area



From ops-area-bounces@ietf.org Thu Sep 20 11:02:34 2007
Return-path: <ops-area-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYNW6-000655-MY; Thu, 20 Sep 2007 11:00:34 -0400
Received: from ops-area by megatron.ietf.org with local (Exim 4.43)
	id 1IYNW4-00063o-V4 for ops-area-confirm+ok@megatron.ietf.org;
	Thu, 20 Sep 2007 11:00:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IYNW4-00063g-LM
	for ops-area@ietf.org; Thu, 20 Sep 2007 11:00:32 -0400
Received: from co300216-co-outbound.net.avaya.com ([198.152.13.100]
	helo=co300216-co-outbound.avaya.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IYNVx-0007PI-Py
	for ops-area@ietf.org; Thu, 20 Sep 2007 11:00:32 -0400
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16])
	by co300216-co-outbound.avaya.com with ESMTP; 20 Sep 2007 11:00:20 -0400
X-IronPort-AV: i="4.20,279,1186372800"; 
	d="url'?txt'208?scan'208,208"; a="67146469:sNHT21334434"
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C7FB96.E1B9CCC1"
Date: Thu, 20 Sep 2007 16:59:44 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0442F394@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
Thread-Topic: I-D ACTION:draft-ietf-opsawg-operations-and-management-00.txt 
Thread-Index: Acf6+3iW7u1v5dLtS+Cr1h/iKZ2zUwAmyEJA
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Subject: [OPS-AREA] FW: I-D
	ACTION:draft-ietf-opsawg-operations-and-management-00.txt 
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Errors-To: ops-area-bounces@ietf.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7FB96.E1B9CCC1
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

=20
The Guidelines for operations and management of new protocols document
was submitted as OPSAWG I-D. Please use the OPSAWG list for comments and
discussions.=20

Dan


=20

-----Original Message-----
From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]=20
Sent: Wednesday, September 19, 2007 10:15 PM
To: i-d-announce@ietf.org
Cc: opsawg@ietf.org
Subject: I-D ACTION:draft-ietf-opsawg-operations-and-management-00.txt=20

A New Internet-Draft is available from the on-line Internet-Drafts
directories.
This draft is a work item of the Operations and Management Area Working
Group Working Group of the IETF.

	Title		: Guidelines for Considering Operations and
Management of New Protocols
	Author(s)	: D. Harrington
	Filename	:
draft-ietf-opsawg-operations-and-management-00.txt
	Pages		: 37
	Date		: 2007-9-19
=09

   New protocols or protocol extensions are best designed with due
   consideration of operations and management issues related to the
   protocol.  Retrofitting operations and management recommendations to
   protocols is sub-optimal.  The purpose of this document is to provide
   guidance to authors of protocol documents about aspects to consider
   related to the operations and management that should be considered
   for inclusion in documents defining requirements or functionality of
   new protocols or protocol extensions.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-opsawg-operations-and-man
agement-00.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request@ietf.org with the word unsubscribe in the body of
the message.=20
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the
username "anonymous" and a password of your e-mail address. After
logging in, type "cd internet-drafts" and then "get
draft-ietf-opsawg-operations-and-management-00.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html or
ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE
/internet-drafts/draft-ietf-opsawg-operations-and-management-00.txt".
=09
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail
readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

------_=_NextPart_001_01C7FB96.E1B9CCC1
Content-Type: application/octet-stream;
	name="ATT849291.TXT"
Content-Transfer-Encoding: base64
Content-Description: ATT849291.TXT
Content-Disposition: attachment;
	filename="ATT849291.TXT"

Q29udGVudC1UeXBlOiBNZXNzYWdlL0V4dGVybmFsLWJvZHk7IGFjY2Vzcy10eXBlPSJtYWlsLXNl
cnZlciI7DQoJc2VydmVyPSJtYWlsc2VydkBpZXRmLm9yZyINCg0KQ29udGVudC1UeXBlOiB0ZXh0
L3BsYWluDQpDb250ZW50LUlEOiA8MjAwNy05LTE5MTUxMjU2LkktREBpZXRmLm9yZz4NCg0KRU5D
T0RJTkcgbWltZQ0KRklMRSAvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWlldGYtb3BzYXdnLW9wZXJh
dGlvbnMtYW5kLW1hbmFnZW1lbnQtMDAudHh0DQo=

------_=_NextPart_001_01C7FB96.E1B9CCC1
Content-Type: application/octet-stream;
	name="draft-ietf-opsawg-operations-and-management-00.URL"
Content-Transfer-Encoding: base64
Content-Description: draft-ietf-opsawg-operations-and-management-00.URL
Content-Disposition: attachment;
	filename="draft-ietf-opsawg-operations-and-management-00.URL"

W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0
cy9kcmFmdC1pZXRmLW9wc2F3Zy1vcGVyYXRpb25zLWFuZC1tYW5hZ2VtZW50LTAwLnR4dA0K

------_=_NextPart_001_01C7FB96.E1B9CCC1
Content-Type: text/plain;
	name="ATT849292.txt"
Content-Transfer-Encoding: base64
Content-Description: ATT849292.txt
Content-Disposition: attachment;
	filename="ATT849292.txt"

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkktRC1Bbm5v
dW5jZSBtYWlsaW5nIGxpc3QNCkktRC1Bbm5vdW5jZUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cxLmll
dGYub3JnL21haWxtYW4vbGlzdGluZm8vaS1kLWFubm91bmNlDQo=

------_=_NextPart_001_01C7FB96.E1B9CCC1
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-area

------_=_NextPart_001_01C7FB96.E1B9CCC1--





From ops-area-bounces@ietf.org Thu Sep 20 18:23:15 2007
Return-path: <ops-area-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IYUNK-0003Z4-A4; Thu, 20 Sep 2007 18:19:58 -0400
Received: from ops-area by megatron.ietf.org with local (Exim 4.43)
	id 1IYUNI-0003KZ-HH for ops-area-confirm+ok@megatron.ietf.org;
	Thu, 20 Sep 2007 18:19:56 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IYUNH-0003BL-QZ
	for ops-area@ietf.org; Thu, 20 Sep 2007 18:19:55 -0400
Received: from pythagoras.zen.co.uk ([212.23.3.140])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IYUNG-0006Qs-V7
	for ops-area@ietf.org; Thu, 20 Sep 2007 18:19:55 -0400
Received: from [88.96.235.138] (helo=cortex.aria-networks.com)
	by pythagoras.zen.co.uk with esmtp (Exim 4.50) id 1IYUNG-000207-6K
	for ops-area@ietf.org; Thu, 20 Sep 2007 22:19:54 +0000
Received: from your029b8cecfe ([81.140.15.32] RDNS failed) by
	cortex.aria-networks.com with Microsoft SMTPSVC(6.0.3790.3959); 
	Thu, 20 Sep 2007 23:19:53 +0100
Message-ID: <003101c7fbd4$5df62740$0200a8c0@your029b8cecfe>
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <dharrington@huawei.com>
References: <EDC652A26FB23C4EB6384A4584434A0442F394@307622ANEX5.global.avaya.com>
Subject: Re: [OPS-AREA] FW:
	I-DACTION:draft-ietf-opsawg-operations-and-management-00.txt 
Date: Thu, 20 Sep 2007 23:15:58 +0100
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.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-OriginalArrivalTime: 20 Sep 2007 22:19:53.0881 (UTC)
	FILETIME=[5E673890:01C7FBD4]
X-Originating-Pythagoras-IP: [88.96.235.138]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
Cc: ops-area@ietf.org
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Errors-To: ops-area-bounces@ietf.org

Hi Dave,

Some thoughts...

The last sentence of the abstract is a bit convoluted. Suggest:
OLD
   The purpose of this document is to provide guidance to authors of
   protocol documents about aspects to consider related to the
   operations and management that should be considered for inclusion in
   documents defining requirements or functionality of new protocols or
   protocol extensions.
NEW
   The purpose of this document is to provide guidance to authors of
   documents that define requirements or functionality of new protocols
   or that define protocol extensions. The guidance is about aspects
   related to operations and management that should be considered for
   inclusion.
===
Introduction. First paragraph.
First sentence rightly refers to new protocols or protocol extensions.
Last sentence refers only to new protocols.
===
   [DISCUSS - This document seems to be just as concerned with the
   protocol designer's "mind-set" and the protocol development process
   as it is with the protocol as a finished product.  While we all agree
   that it would be a good thing to imprint operational sensitivities
   into the consciousness of the protocol developer, I do not think that
   this is a practical goal.  The best that we can do is to set forth a
   list of objective criteria by which a protocol designer can evaluate
   whether the protocol that he/she has developed is manageable.]
I think this point is worth crystalising in the text. But we shoud also
give some guidance about things to include/exclude in order to achieve
the goal of being manageable.
===
   [DISCUSS: - the document may attempt to cover too much ground.  Maybe
   it will develop into a framework document, supported by documents of
   the following sort: . what makes a MIB usable? . how much protocol
   state information needs to be exposed and how? . how much performance
   information needs to be exposed and how?]
Certainly too much detail will render the document unreadable by all but
the management geeks (who we assume are already the converted in this
matter. Better to be short and pithy with pointers to more information
on specific topics in different places.
In fact, a good piece of the docment seems to be about the philosophy
underlying the giving of guidance. maybe that should be separated from
the guidance itself and the philosophy underlying the guidance.
My feeling is that, at 37 pages, it is already unlikely to be read by
many people. That may be unfortunate, but it fact. I think you have to
get your base document down to around 15 pages.
===
   Experiments
   to require such sections have had a mixed reaction from protocol
   developers.
Not for inclusion in the I-D, but have you any details of negative
reactions to such experiments?
===
Section 4 (maybe 4.1?)
It might be interesting to consider extensibility. For example, a MIB
module structure that is open to future protocol extensions or to
proprietary extensions provide greater manageability.
===
Section 4.3.1
   [DISCUSS:: 'control plane' and 'data plane' are such slippery terms
   that I think they need to be defined.]
Probably, this being mainly an IP-centric world, you could use:
- control protocol fault
- data forwarding fault
===
Sections 4.6, 6.5, and 9
I find the subtly of difference between 4.6 and 6.5 hard. Could the
sections reference each other for some clarification?
I think section 9 should at least reference 4.6 and 6.5.
But we also need to consider security vulnerabilities introduced by
management techniques. For example, if you cannot configure a router, it
is hard to make it do bad things. For example, OAM techniques can be
used to swamp the forwarding plane achieving a DoS attack.
===

Hope this is useful.

Cheers,
Adrian 




_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-area



From ops-area-bounces@ietf.org Mon Sep 24 04:07:58 2007
Return-path: <ops-area-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IZiwS-0006mF-7o; Mon, 24 Sep 2007 04:05:20 -0400
Received: from ops-area by megatron.ietf.org with local (Exim 4.43)
	id 1IZiwR-0006jN-Iq for ops-area-confirm+ok@megatron.ietf.org;
	Mon, 24 Sep 2007 04:05:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IZiwN-0006ey-Fj
	for ops-area@ietf.org; Mon, 24 Sep 2007 04:05:15 -0400
Received: from [198.152.71.100] (helo=de307622-de-outbound.net.avaya.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IZiwH-0007O0-2N
	for ops-area@ietf.org; Mon, 24 Sep 2007 04:05:15 -0400
X-IronPort-AV: E=Sophos;i="4.20,290,1186372800"; d="scan'208";a="60483366"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16])
	by de307622-de-outbound.net.avaya.com with ESMTP;
	24 Sep 2007 04:04:09 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 24 Sep 2007 10:03:28 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0446F48C@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: DHC recharter
Thread-Index: Acf+GG1GMP7raXYVSFOxtE/U+5MkHQAaNc4w
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f
Subject: [OPS-AREA] FW: DHC recharter
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Errors-To: ops-area-bounces@ietf.org

=20
Comments from the OPS area would be welcome.=20

Dan


=20

-----Original Message-----
From: Jari Arkko [mailto:jari.arkko@piuha.net]=20
Sent: Sunday, September 23, 2007 9:31 PM
To: IESG; IAB
Cc: Dhc Chairs
Subject: DHC recharter


Secretary (Bcced),

Please put DHC WG rechartering to the next IESG telechat agenda. (Under
category "consideration for IETF review".)

IESG, IAB: this is a fairly major update of the DHC charter.
The new charter has more specific rules about what the group can and
cannot do with regards to DHC option development. And there's an updated
specification of how DHC WG and other WGs work together when a new
option is needed.

Work that has been completed has been taken out of the charter. Work
that has not generated enough energy has been taken out.

I see no evidence of interest in DHCP security, other than the DSL Forum
demands, but I think we should take those separately. (I.e., decide
whether those make sense and if they do, recharter again.) As a result
we have taken out the authentication work entirely.

Comments appreciated. The charter has been discussed in the WG list and
in one of the previous meetings; the version below is a changed one
based on discussions between the chairs and the AD. It has also been
posted for WG comment; I expect that to conclude before our next
telechat.

Jari

----

The dhc working group (DHC WG) has developed DHCP for automated
allocation, configuration and management of IP addresses and TCP/IP
protocol stack parameters. DHCPv4 is currently a "Draft Standard" and is
documented in RFC 2131 and RFC 2132.  DHCPv6 is currently a "Proposed
Standard" and is documented in RFC 3315.  Subsequent RFCs document
additional options and other enhancements to the specifications.

The DHC WG is responsible for reviewing DHCP options or other extensions
(for both IPv4 and IPv6). The DHC WG is expected to review all proposed
extensions to DHCP to ensure that they are consistent with the DHCP
specification and other option formats, that they do not duplicate
existing mechanisms, etc.  Generally speaking, the DHC WG will not be
responsible for evaluating the semantic content of proposed options.
Similarly, the ownership of specifications typically belongs the
relevant working group that needs more functionality from DHCP, not the
DHC WG. The DHC WG coordinates reviews of the proposed options together
with those working groups. It is required that those working groups have
consensus to take on the work and that the work is within their charter.
Exceptionally, with AD agreement, this same process can also be used for
Individual Submissions originating outside WGs.

However, the DHC WG can in some cases develop its own options that
relate to either maintenance of existing specifications or improvements
in the operation of the DHCP infrastructure itself.

The DHC WG has the following main objectives:

* Develop extensions to the DHCP infrastructure as required to meet
  new applications and deployments of DHCP. The topics currently
  in development are:

    - Subnet allocation mechanisms
    - Virtual subnet identification option
    - Option for passing DNS domain information in DHCPv6
    - DHCP relay agent assignment notification in DHCPv6
    - Option for DHCPv6 server reply sequence numbers
    - Rebinding capability for DHCPv6 Reconfigure messages

  The adoption of new items requires explicit agreement from
  the AD or rechartering.

* Write analyses of the DHCPv4 and DHCPv6 specifications,
  including RFC 2131, RFC 2132, RFC 3315 and other RFCs defining
  additional options, which identifies ambiguities, contradictory
  specifications and other obstacles to development of interoperable
  implementations. Recommend a process for resolving identified
  problems and incorporating the resolutions into the DHCP
  specification.

  Secondly, advance DHCPv4 (RFC 2131 and RFC 2132) and DHCPv6 (RFC
  3315) in IETF Standards Track.

  Thirdly, specify guidelines for creating new DHCP options.

* Assess the requirements for a dual-stack host to use DHCP to obtain
  configuration settings for both IPv4 and IPv6.  Hosts that include
  implementations of both IPv4 and IPv6 ("dual-stack hosts") may use
  DHCP to obtain configuration settings (including assigned addresses)
  for both IPv4 and IPv6.  The DHCPv4 and DHCPv6 specifications (RFC
  2131, RFC 2132, RFC 3315 and subsequent RFCs) do not explicitly
  explain how a dual-stack host uses DHCP to obtain configuration
  settings for both IP stacks.  The DHC WG will evaluate solutions for
  configuration of dual-stack hosts through DHCP and select a solution
  that will be developed and published by the WG.

Milestones:

Done   WG last call for "Subnet Allocation Option"
       <draft-ietf-dhc-subnet-alloc-04>
Done   WG last call on "Virtual Subnet Selection Option",
       <draft-ietf-dhc-vpn-option>
Oct 07 Submit "Subnet Allocation Option"
       <draft-ietf-dhc-subnet-alloc-04> to IESG
       for Proposed Standard
Nov 07 WG last call on "Guidelines for Creating New DHCP Options"
       <draft-ietf-dhc-option-guidelines>
Nov 07 Submit "Virtual Subnet Selection Option",
       <draft-ietf-dhc-vpn-option> and <draft-ietf-dhc-agent-vpn-id>
       to IESG for Proposed Standard
Dec 07 WG last call for "Domain Suffix Option for DHCPv6"
       <draft-ietf-dhc-dhcpv6-opt-dnsdomain>
Jan 08 Submit "Domain Suffix Option for DHCPv6"
       <draft-ietf-dhc-dhcpv6-opt-dnsdomain> to IESG
       for Proposed Standard
Jan 08 Submit "Guidelines for Creating New DHCP Options"
       <draft-ietf-dhc-option-guidelines> to IESG for Best Current
       Practice
Jan 08 Develop plan for advancing DHCPv4 and DHCPv6; plan to include
       completion of DHCPv4 specification review report,
       "Implementation Issues with RFC 2131"
       <draft-ietf-dhc-implementation-02> for Informational Feb 08 WG
last call for "Dual-stack clients and merging of data from
       DHCPv4 and DHCPv6" <draft-ietf-dhc-dual-stack-merge-01.txt>;
       waiting for more experience with IPv6 deployment Feb 08 WG last
call for "Rebind Capability in DHCPv6 Reconfigure
       Messages" <draft-ietf-dhc-dhcpv6-reconfigure-rebind-00>
Apr 08 2nd WG last call for "DHCP Relay Agent Assignment Notification
       Option" <draft-ietf-dhc-dhcpv6-agentopt-delegate-01> and
       "DHCPv6 Server Reply Sequence Number Option"
       <draft-ietf-dhc-dhcpv6-srsn-option-00>
May 08 Submit "Rebind Capability in DHCPv6 Reconfigure Messages"
       <draft-ietf-dhc-dhcpv6-reconfigure-rebind-00> to IESG for
       Proposed Standard
Jul 08 Submit "DHCP Relay Agent Assignment Notification Option"
       <draft-ietf-dhc-dhcpv6-agentopt-delegate-01> and "DHCPv6 Server
       Reply Sequence Number Option"
       <draft-ietf-dhc-dhcpv6-srsn-option-00> to IESG for
       Proposed Standard
Jul 08 Recharter for more work



_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-area



From ops-area-bounces@ietf.org Tue Sep 25 12:38:31 2007
Return-path: <ops-area-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IaDNZ-0008GI-EC; Tue, 25 Sep 2007 12:35:21 -0400
Received: from ops-area by megatron.ietf.org with local (Exim 4.43)
	id 1IaDNY-0008Fz-70 for ops-area-confirm+ok@megatron.ietf.org;
	Tue, 25 Sep 2007 12:35:20 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IaDNX-0008Fr-T8
	for ops-area@ietf.org; Tue, 25 Sep 2007 12:35:19 -0400
Received: from co300216-co-outbound.net.avaya.com ([198.152.13.100]
	helo=co300216-co-outbound.avaya.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IaDNX-0004tT-IF
	for ops-area@ietf.org; Tue, 25 Sep 2007 12:35:19 -0400
X-IronPort-AV: E=Sophos;i="4.20,296,1186372800"; d="scan'208";a="69002546"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16])
	by co300216-co-outbound.avaya.com with ESMTP; 25 Sep 2007 12:35:18 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 25 Sep 2007 18:34:37 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0446F9AC@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [RAI] Announcement of RAI Review Directorate
Thread-Index: Acf+44p+iaMpQGUNRiqYJIG/zL2dbgArmI6Q
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Subject: [OPS-AREA] FW: [RAI] Announcement of RAI Review Directorate
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Errors-To: ops-area-bounces@ietf.org

=20


=20

-----Original Message-----
From: Cullen Jennings [mailto:fluffy@cisco.com]=20
Sent: Monday, September 24, 2007 9:41 PM
To: rai@ietf.org
Subject: [RAI] Announcement of RAI Review Directorate


Hi All,

After many discussions we have formed an RAI area review team. You can
read more about it at the links below but at a high level the goal of
this is to provide a resource that chairs can use when they feel
additional review would be beneficial - typically around the time a
document was adopted as a WG item. It does not change the process in any
way and it's not something that has to be done for every document - it's
just a resource to use when it can help.

Have a read of links provided and many thanks to Mary Barnes.


Guidelines at http://www.softarmor.com/rai/art/review-guidelines.html

FAQ at http://www.softarmor.com/rai/art/FAQ.html

Members at http://www.softarmor.com/rai/art/rai-reviewer-list.html

_______________________________________________
RAI mailing list
RAI@ietf.org
https://www1.ietf.org/mailman/listinfo/rai


_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-area



From ops-area-bounces@ietf.org Wed Sep 26 15:26:03 2007
Return-path: <ops-area-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1IacTF-0005yy-Uh; Wed, 26 Sep 2007 15:22:53 -0400
Received: from ops-area by megatron.ietf.org with local (Exim 4.43)
	id 1IacTE-0005yh-De for ops-area-confirm+ok@megatron.ietf.org;
	Wed, 26 Sep 2007 15:22:52 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1IacTE-0005xz-1R
	for ops-area@ietf.org; Wed, 26 Sep 2007 15:22:52 -0400
Received: from co300216-co-outbound.net.avaya.com ([198.152.13.100]
	helo=co300216-co-outbound.avaya.com)
	by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IacTC-0004Km-Ve
	for ops-area@ietf.org; Wed, 26 Sep 2007 15:22:51 -0400
X-IronPort-AV: E=Sophos;i="4.21,198,1188792000"; d="scan'208";a="69470786"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16])
	by co300216-co-outbound.avaya.com with ESMTP; 26 Sep 2007 15:22:50 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 26 Sep 2007 21:22:06 +0200
Message-ID: <EDC652A26FB23C4EB6384A4584434A0446FB9C@307622ANEX5.global.avaya.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: REMINDER - 70th IETF - Working Group/BOF Scheduling 
Thread-Index: AcgAbzvXHFsbxcolRqaD3KP3CmvjOgAA0R3w
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <ops-area@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1094b1c84fa6e846d476f39271f5074f
Subject: [OPS-AREA] REMINDER - 70th IETF - Working Group/BOF Scheduling 
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Errors-To: ops-area-bounces@ietf.org

=20


=20

-----Original Message-----
From: IETF Agenda [mailto:agenda@ietf.org]=20
Sent: Wednesday, September 26, 2007 8:57 PM
To: wgchairs@ietf.org; bofchairs@ietf.org; irsg@isi.edu
Subject: [BOFCHAIRS] REMINDER - 70th IETF - Working Group/BOF Scheduling


-----------------------------------------------------------------
70th IETF - Vancouver, BC, Canada
Meeting Dates: December 2-7, 2007
-----------------------------------------------------------------
We will be accepting scheduling requests for all Working Groups and BOFs
starting today, Tuesday, September 4, 2007.  The milestones and
deadlines for scheduling-related activities are as follows:

-- Cut-off date for requests to schedule Working Group meetings and for
preliminary BOF proposals to ADs: Monday, October 1 at 17:00 ET (21:00
UTC/GMT).
-- Cut-off date for requests to schedule BoFs: Monday, October 22 at
17:00 ET (21:00 UTC/GMT).
-- Preliminary agenda published for comment: Friday, October 26 by
midnight ET.
-- Cut-off date for requests to reschedule Working Group and BOF
meetings:
Wednesday, November 7 at 09:00 ET (14:00 UTC/GMT).
-- Final agenda published: Monday, November 12 before midnight ET.
-- Draft Working Group agendas due: Wednesday, November 21 at 17:00 ET
(22:00 UTC/GMT).
-- Revised Working Group agendas due: Monday, November 26 at 12:00 ET
(17:00 UTC/GMT), upload using IETF Meeting Materials Management Tool

Submitting Requests for Working Group and BOF Sessions

Please submit requests to schedule your Working Group sessions using the
"IETF Meeting Session Request Tool," a Web-based tool for submitting all
of the information that the Secretariat requires to schedule your
sessions.

The URL for the tool is:

https://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi

Instructions for using the tool are available at:

http://www.ietf.org/instructions/session_request_tool_instruction.html

Please send requests to schedule your BOF sessions to agenda at
ietf.org.
=20
Please include the acronym of your BOF in the subject line of the
message, and include all of the information specified in item (4) of
"Requesting Meeting Sessions at IETF Meetings" in the body.  (This
document is included below.)

Submitting Session Agendas

For the convenience of meeting attendees, we ask that you submit the
agendas for your Working Group sessions as early as possible.  Draft
Working Group agendas are due Wednesday, November 21 by 17:00 ET (22:00
UTC/GMT).  Revised Working Group agendas are due no later than Monday,
November 26 at 12:00 ET (17:00 UTC/GMT).  The proposed agenda for a BOF
session should be submitted along with your request for a session.
Please be sure to copy your Area Director on that message.

Please submit the agendas for your Working Group sessions using the
"IETF Meeting Materials Management Tool," a Web-based tool for making
your meeting agenda, minutes, and presentation slides available to the
community before, during, and after an IETF meeting.  If you are a BOF
chair, then you may use the tool to submit a revised agenda as well as
other materials for your BOF once the BOF has been approved.

The URL for the tool is:

https://datatracker.ietf.org/cgi-bin/wg/wg_proceedings.cgi

Additional information about this tool is available at:

http://www.ietf.org/instructions/meeting_materials_tool.html

Agendas submitted via the tool will be available to the public on the
"IETF Meeting Materials" Web page as soon as they are submitted.

The URL for the "IETF 70 Meeting Materials" Web page is:

https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=3D7=
0

If you are a Working Group chair, then you already have accounts on the
"IETF Meeting Session Request Tool" and the "IETF Meeting Materials
Management Tool."  The same User ID and password will work for both
tools.

  If you are a BOF chair who is not also a Working Group chair, then you
will be given an account on the "IETF Meeting Materials Management Tool"
when your BOF has been approved.  If you require assistance in using
either tool, or wish to report a bug, then please send a message to:
ietf-action at ietf.org.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
For your convenience, comprehensive information on requesting meeting
sessions at IETF 70 is presented below:

1. Requests to schedule Working Group sessions should be submitted using
the "IETF Meeting Session Request Tool," a Web-based tool for submitting
all of the information required by the Secretariat to schedule your
sessions.  The URL for the tool is:

https://datatracker.ietf.org/cgi-bin/wg/wg_session_requester.cgi

Instructions for using the tool are available at:

http://www.ietf.org/instructions/session_request_tool_instruction.html

If you require an account on this tool, or assistance in using it, then
please send a message to ietf-action at ietf.org.  If you are unable to
use the tool, then you may send your request via e-mail to agenda at
ietf.org, with a copy to the appropriate Area Director(s).

Requests to schedule BOF sessions must be sent to agenda at ietf.org
with a copy to the appropriate Area Director(s).

When submitting a Working Group or BOF session request by e-mail, please
include the Working Group or BOF acronym in the Subject line.

2. BOFs will NOT be scheduled unless the Area Director(s) approved
request is accompanied by a BOF'S FULL NAME AND ACRONYM, AREA, CHAIR(S)
NAME(S) (given together with e-mail address(es)), AN AGENDA AND FULL
DESCRIPTION, and the information requested in (4) below. (Please read
the BOF Procedure at: http://www.ietf.org/ietf/1bof-procedures.txt
before requesting a session for a BOF.)

3. A Working Group may request either one or two sessions.  If your
Working Group requires more than two sessions, then your request must be
approved by an Area Director.  Additional sessions will be assigned,
based on availability, after Wednesday, November 7 at 09:00 ET (14:00
UTC/GMT), the cut-off date for requests to reschedule a session.

4. You MUST provide the following information before a Working Group or
BOF session will be scheduled:

    a. Working Group or BOF full name with acronym in brackets:=20

    b. AREA under which Working Group or BOF appears:

    c. CONFLICTS you wish to avoid, please be as specific as possible:

    d. Expected Attendance (figures from the 69th IETF meeting are
included at the end of this message):

    e. Special requests:

    f. Number of sessions:

    g. Length of session:=20
       - 1 hour=20
       - 2 hours=20
       - 2 1/2 hours

For more information on scheduling Working Group and BOF sessions,
please refer to RFC 2418 (BCP 25), "IETF Working Group Guidelines and
Procedures"
(http://www.ietf.org/rfc/rfc2418.txt).
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
For your convenience please find here a list of the IETF Area Directors
with their e-mail addresses:

IETF Chair
Russ Housley <housley at vigilsec.com>

Applications Area (app)
Lisa Dusseault <lisa at osafoundation.org> Chris Newman <chris.newman at
sun.com>

Internet Area (int)
Jari Arkko <jari.arkko at piuha.net>
Mark Townsley <townsley at cisco.com>

Operations & Management Area (ops)
Ronald Bonica <rbonica at juniper.net>
Dan Romascanu <dromasca at avaya.com>

Real-time Applications and Infrastructure Area (rai) Cullen Jennings
<fluffy at cisco.com> Jon Peterson <jon.peterson at neustar.biz>

Routing Area (rtg)
Ross Callon <rcallon at juniper.net>
David Ward <dward at cisco.com>

Security Area (sec)
Sam Hartman <hartmans-ietf at mit.edu>
William Polk <wpolk at nist.gov>

Transport Area (tsv)
Lars Eggert <eggert at nokia.com>
Magnus Westerlund <magnus.westerlund at ericsson.com>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D
69th IETF Meeting Attendance Number

16ng	66
6lowpan	No Blue Sheets
ancp	No Blue Sheets
apm (BoF)	93
apparea (AG)	75
autoconf	77
autoconf (2nd session)	63
avt	94
avt (2nd session)	73
behave	53
biff (BoF)	30
bliss	123
bmwg	38
btns	38
calcify	14
capwap	44
ccamp	112
ccamp (2nd session)	95
dccp	33
dhc	66
dime	35
dkim	58
dnsop	104
dtnrg	51
eai	47
ecrit	93
emu	39
enum	82
forces	17
geopriv	100
grow	73
hiprg/emerg	77
hokey	87
httpbis (BoF)	61
iccrg	52
idr	112
intarea (AG)	120
ipdvb	7
ipfix	24
ippm	No Blue Sheets
ipr	23
isis	58
isms	25
keyprov 	46
kitten	17
krb-wg	32
krb-wg (2nd session)	21
l1vpn	CANCELLED
l2vpn	No Blue Sheets
l3vpn	83
lemonade	35
lemonade (2nd session)	25
ltans	16
manet	77
mboned	50
mediactrl	42
mip4	31
mip6	101
mipshop	100
mmusic	42
mmusic (2nd session)	77
mobopts (RG)	85
monami6	90
mpls	152
nea	62
nee (BoF)	46
nemo	92
netconf	38
netlmm	99
nfsv4	20
nsis	36
ntp	37
opsawg	66
ospf	56
p2psip (adhoc)	36
p2psip	154
pana	34
pce	63
pcn	79
pim	32
pkix	52
pwe3	127
radext	39
rmt	32
rpsec	50
rrg	145
rtgarea (AG)	136
rtgwg	97
saag (AG)	149
samrg	41
sasl	31
sidr	89
sieve	17
simple	81
sip 	162
sip (2nd session)	128
sipping	137
sipping (2nd session)	135
smime	17
softwire	51
speermint	125
tam (BoF)	103
tcpm	35
tls	54
trill	44
trill (2nd session)	27
tsvarea (AG)	67
tsvwg	81
v6ops	130
vcarddav (BoF)	24
xcon	45
xsdmi (BoF)	29


_______________________________________________
BOFCHAIRS mailing list
BOFCHAIRS@ietf.org
https://www1.ietf.org/mailman/listinfo/bofchairs


_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-area



From ops-area-bounces@ietf.org Thu Sep 27 07:36:58 2007
Return-path: <ops-area-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Iarcv-0001hM-4D; Thu, 27 Sep 2007 07:33:53 -0400
Received: from ops-area by megatron.ietf.org with local (Exim 4.43)
	id 1Iarct-0001f7-P6 for ops-area-confirm+ok@megatron.ietf.org;
	Thu, 27 Sep 2007 07:33:51 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Iarcs-0001WY-BG; Thu, 27 Sep 2007 07:33:50 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1Iarck-00033e-3k; Thu, 27 Sep 2007 07:33:48 -0400
Received: from mailgw3.ericsson.se (unknown [127.0.0.1])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	5686120B72; Thu, 27 Sep 2007 13:33:31 +0200 (CEST)
X-AuditID: c1b4fb3c-afe7ebb0000007e1-90-46fb950b7cdf
Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122])
	by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id
	3455720B6C; Thu, 27 Sep 2007 13:33:31 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 27 Sep 2007 13:33:31 +0200
Received: from [147.214.30.247] ([147.214.30.247]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Thu, 27 Sep 2007 13:33:30 +0200
Message-ID: <46FB950A.6020401@ericsson.com>
Date: Thu, 27 Sep 2007 13:33:30 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Internet Area <int-area@ietf.org>,  ops-area@ietf.org, 
	discuss@apps.ietf.org, routing-discussion@ietf.org, SAAG <saag@mit.edu>
X-Enigmail-Version: 0.95.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 27 Sep 2007 11:33:30.0993 (UTC)
	FILETIME=[3AE46610:01C800FA]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: -1.0 (-)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: tsvwg <tsvwg@ietf.org>
Subject: [OPS-AREA] Guidelines for protocol designers using UDP
X-BeenThere: ops-area@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: tsvwg <tsvwg@ietf.org>
List-Id: OPS Area e-mail list <ops-area.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ops-area>
List-Post: <mailto:ops-area@ietf.org>
List-Help: <mailto:ops-area-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ops-area>,
	<mailto:ops-area-request@ietf.org?subject=subscribe>
Errors-To: ops-area-bounces@ietf.org

Hi,

In the TSVWG we have been developing a guidelines document for UDP. It
is intended for protocol designers that consider using UDP in their
protocol. We do hope that it will help remove some of the misconception
that UDP is a simple protocol to use. It might look that way because
most of the features necessary for being acceptable to deploy on the
general internet needs to be specified by the one using UDP. It is also
something that the Transport ADs already started using as help in
explaining why and what to fix when we put a DISCUSS on your document
that is using UDP.

http://www.ietf.org/internet-drafts/draft-ietf-tsvwg-udp-guidelines-03.txt

So TSVWG is still working on this document but we are now considering it
quite complete. So we are looking for feedback from you. Are there
things that are unclear, missing, wrong, etc. Please provide your
feedback to TSVWG (tsvwg@ietf.org).

Thanks

Magnus Westerlund

IETF Transport Area Director & TSVWG Chair
----------------------------------------------------------------------
Multimedia Technologies, Ericsson Research EAB/TVM/M
----------------------------------------------------------------------
Ericsson AB                | Phone +46 8 4048287
Torshamsgatan 23           | Fax   +46 8 7575550
S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------



_______________________________________________
OPS-AREA mailing list
OPS-AREA@ietf.org
https://www1.ietf.org/mailman/listinfo/ops-area



