From mobopts-bounces@irtf.org Thu Feb 16 13:13:49 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1F9ndV-000655-5a; Thu, 16 Feb 2006 13:13:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1F9ndO-00061V-Vh
	for mobopts@megatron.ietf.org; Thu, 16 Feb 2006 13:13:44 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17474
	for <mobopts@irtf.org>; Thu, 16 Feb 2006 13:11:55 -0500 (EST)
Received: from oak.research.panasonic.com ([150.169.1.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F9nrf-0007ch-HJ
	for mobopts@irtf.org; Thu, 16 Feb 2006 13:28:28 -0500
Received: from redwood.research.panasonic.com (redwood.research.panasonic.com
	[150.169.3.3])
	by oak.research.panasonic.com (1.1.1/1.1.1) with ESMTP id
	k1GIDWuC008093
	for <mobopts@irtf.org>; Thu, 16 Feb 2006 13:13:32 -0500
Received: from redwood.research.panasonic.com (redwood.research.panasonic.com
	[150.169.3.3])
	by testing.research.panasonic.com (Postfix) with ESMTP id C15CE3C81EF
	for <mobopts@irtf.org>; Thu, 16 Feb 2006 13:10:54 -0500 (EST)
Received: from [150.169.1.178] (video.Research.Panasonic.COM 
	[150.169.1.178])by redwood.research.panasonic.com (Postfix) with ESMTP
	id 
	B08B83C81E7for <mobopts@irtf.org>; Thu, 16 Feb 2006 13:10:54 -0500 (EST)
Message-ID: <43F4C04A.9030807@research.panasonic.com>
Date: Thu, 16 Feb 2006 13:11:22 -0500
From: Greg Daley <gregd@research.panasonic.com>
User-Agent: Thunderbird 1.5 (Windows/20051201)
MIME-Version: 1.0
To: mobopts@irtf.org
X-Enigmail-Version: 0.94.0.0
Content-Type: multipart/mixed;
	boundary=------------010806020001070901010602
X-imss-version: 2.8
X-imss-result: Passed
X-imss-scores: Clean:57.65382 C:17 M:2 S:5 R:5
X-imss-settings: Baseline:1 C:1 M:1 S:1 R:1 (0.0000 0.0000)
X-Spam-Score: 2.5 (++)
X-Scan-Signature: 7a0494a0224ca59418dd8f92694c1fdb
Subject: [Mobopts] draft-vogt-mobopts-simple-cba-00.txt
X-BeenThere: mobopts@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP Mobility Optimizations <mobopts.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mobopts>,
	<mailto:mobopts-request@irtf.org?subject=unsubscribe>
List-Post: <mailto:mobopts@irtf.org>
List-Help: <mailto:mobopts-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mobopts>,
	<mailto:mobopts-request@irtf.org?subject=subscribe>
Sender: mobopts-bounces@irtf.org
Errors-To: mobopts-bounces@irtf.org

This is a multi-part message in MIME format.
--------------010806020001070901010602
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi,

I just read the draft of the new CBA, and think it's
in good shape to progress toward publication.
It looks like the document has been made
straightforward and concise.

What's the plan?

Is the aim to get it put out as an experimental RFC
here, or get the document adopted and reviewed in IETF?

Greg

--------------010806020001070901010602
Content-Type: message/rfc822;
	name="I-D ACTION:draft-vogt-mobopts-simple-cba-00.txt"
Content-Disposition: inline;
	filename="I-D ACTION:draft-vogt-mobopts-simple-cba-00.txt"

Return-path: <i-d-announce-bounces@ietf.org>
Received: from oak.research.panasonic.com
	(oak.Research.Panasonic.COM [150.169.1.4])
	by pintlmail.MITL.Research.Panasonic.COM
	(iPlanet Messaging Server 5.2 HotFix 1.09 (built Jan  7 2003))
	with ESMTP id <0IUR00JIA6FP7I@pintlmail.MITL.Research.Panasonic.COM>
	for gregd@ims-ms-daemon; Wed, 15 Feb 2006 18:55:01 -0500 (EST)
Received: from redwood.research.panasonic.com
	(redwood.research.panasonic.com [150.169.3.3])	by
	oak.research.panasonic.com
	(1.1.1/1.1.1) with ESMTP id k1FNt1wM024842	for
	<gregd@research.panasonic.com>; Wed, 15 Feb 2006 18:55:01 -0500
Received: from redwood.research.panasonic.com
	(redwood.research.panasonic.com [150.169.3.3])
	by testing.research.panasonic.com (Postfix) with ESMTP id
	C639B3C8187	for
	<gregd@research.panasonic.com>; Wed, 15 Feb 2006 18:54:31 -0500 (EST)
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by	redwood.research.panasonic.com (Postfix) with ESMTP id
	6C0243C8195for
	<gregd@research.panasonic.com>; Wed, 15 Feb 2006 18:54:28 -0500 (EST)
Received: from localhost.cnri.reston.va.us ([127.0.0.1]	helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)id	1F9WPr-0002Pz-5b; Wed,
	15 Feb 2006 18:50:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by	megatron.ietf.org with esmtp (Exim 4.32)
	id 1F9WPV-00026G-Trfor	i-d-announce@megatron.ietf.org; Wed,
	15 Feb 2006 18:50:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org	(8.9.1a/8.9.1a) with ESMTP id SAA18901for
	<i-d-announce@ietf.org>; Wed, 15 Feb 2006 18:48:26 -0500 (EST)
Received: from pine.neustar.com ([209.173.57.70])by ietf-mx.ietf.org with	esmtp
	(Exim 4.43) id 1F9Wda-0007aV-2ufor i-d-announce@ietf.org; Wed,
	15 Feb 2006 19:04:49 -0500
Received: from stiedprstage1.ietf.org
	(stiedprstage1.va.neustar.com[10.31.47.10])by
	pine.neustar.com	(8.12.8/8.12.8) with ESMTP id
	k1FNo1vP010598(version=TLSv1/SSLv3	cipher=DHE-RSA-AES256-SHA bits=256
	verify=NOT)for <i-d-announce@ietf.org>;
	Wed, 15 Feb 2006 23:50:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id	1F9WPJ-0001V2-Iwfor i-d-announce@ietf.org;
	Wed, 15 Feb 2006 18:50:01 -0500
Date: Wed, 15 Feb 2006 18:50:01 -0500
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-vogt-mobopts-simple-cba-00.txt
Sender: i-d-announce-bounces@ietf.org
To: i-d-announce@ietf.org
Errors-to: i-d-announce-bounces@ietf.org
Reply-to: internet-drafts@ietf.org
Message-id: <E1F9WPJ-0001V2-Iw@stiedprstage1.ietf.org>
MIME-version: 1.0
Content-type: Multipart/Mixed; Boundary=NextPart
Precedence: list
X-BeenThere: i-d-announce@ietf.org
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
X-imss-version: 2.8
X-imss-result: Passed
X-imss-scores: Clean:99.90000 C:17 M:1 S:5 R:5
X-imss-settings: Baseline:2 C:1 M:2 S:2 R:1 (0.1500 0.1500)
X-Mailman-Version: 2.1.5
List-Post: <mailto:i-d-announce@ietf.org>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mailt	o:i-d-announce-request@ietf.org?subject=subscribe>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/i-d-announce>,
	<mai	lto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Id: i-d-announce.ietf.org
Original-recipient: rfc822;gregd@pintlmail.mitl.research.panasonic.com

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Credit-Based Authorization for Concurrent Reachability Verification

	Author(s)	: C. Vogt, J. Arkko
	Filename	: draft-vogt-mobopts-simple-cba-00.txt
	Pages		: 19
	Date		: 2006-2-15
	

   Mobility and multi-homing protocols enable multi-addressed nodes to
   redirect ongoing communication sessions from one IP address to
   another.  Most of these protocols verify a multi-addressed node's
   reachability at a claimed new IP address in order to prevent
   redirection-based flooding attacks.  In view of reduced protocol
   latencies, such verification is preferably performed concurrently,
   i.e., while packets are already being sent to the new IP address.
   This document defines Credit-Based Authorization, a technique that
   facilitates concurrent reachability verification without compromise
   of security.



A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-vogt-mobopts-simple-cba-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.  
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-vogt-mobopts-simple-cba-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-vogt-mobopts-simple-cba-00.txt".
	
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
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2006-2-15161537.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-vogt-mobopts-simple-cba-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-vogt-mobopts-simple-cba-00.txt"; site="ftp.ietf.org";
	access-type="anon-ftp"; directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2006-2-15161537.I-D@ietf.org>


--OtherAccess--
--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce

--NextPart--
--------------010806020001070901010602
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Mobopts mailing list
Mobopts@irtf.org
https://www1.ietf.org/mailman/listinfo/mobopts

--------------010806020001070901010602--




From mobopts-bounces@irtf.org Tue Feb 21 02:32:41 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FBS0m-0003uA-CQ; Tue, 21 Feb 2006 02:32:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FBS0m-0003u4-0A
	for mobopts@irtf.org; Tue, 21 Feb 2006 02:32:40 -0500
Received: from iramx1.ira.uni-karlsruhe.de ([141.3.10.80])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FBS0k-0006dp-MJ
	for mobopts@irtf.org; Tue, 21 Feb 2006 02:32:39 -0500
Received: from i72ms2.tm.uni-karlsruhe.de ([141.3.70.17]
	helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by iramx1.ira.uni-karlsruhe.de with esmtps 
	id 1FBS0V-000478-K7; Tue, 21 Feb 2006 08:32:28 +0100
Received: from [IPv6:2001:638:204:6:20c:6eff:fe40:8d95]
	(archimedes.ipv6.tm.uni-karlsruhe.de
	[IPv6:2001:638:204:6:20c:6eff:fe40:8d95])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id 5AA268541;
	Tue, 21 Feb 2006 08:32:22 +0100 (CET)
Message-ID: <43FAC206.6060900@tm.uka.de>
Date: Tue, 21 Feb 2006 08:32:22 +0100
From: Christian Vogt <chvogt@tm.uka.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE;
	rv:1.7.12) Gecko/20050923 Thunderbird/1.0.7 Mnenhy/0.7.2.0
X-Accept-Language: de-DE, de, en-us, en
MIME-Version: 1.0
To: Greg Daley <gregd@research.panasonic.com>
Subject: Re: [Mobopts] draft-vogt-mobopts-simple-cba-00.txt
References: <43F4C04A.9030807@research.panasonic.com>
In-Reply-To: <43F4C04A.9030807@research.panasonic.com>
X-Enigmail-Version: 0.90.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -5.0 (-----)
X-Spam-Status: No
X-Spam-Report: -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP
	-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	-0.6 AWL AWL: From: address is in the auto white-list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: mobopts@irtf.org
X-BeenThere: mobopts@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP Mobility Optimizations <mobopts.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mobopts>,
	<mailto:mobopts-request@irtf.org?subject=unsubscribe>
List-Post: <mailto:mobopts@irtf.org>
List-Help: <mailto:mobopts-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mobopts>,
	<mailto:mobopts-request@irtf.org?subject=subscribe>
Errors-To: mobopts-bounces@irtf.org

Hi Greg,

sorry for the late response.  Was out of town for a few days.

Yes, the intention for writing draft-vogt-mobopts-simple-cba-00.txt was 
to finally provide a document that is ready for publication.

"Simple CBA" refers to the basic (and easy-to-implement) mode where the 
correspondent node measures a mobile node's effort in terms of the 
packets received from that mobile node.  I got the impression that this 
mode seems to be widely considered mature in the community now.

Simple CBA is a product of the Mobopts Research Group.  And so is the 
rest of CBA, which is a bit less simply and more researchy, though. 
Hence, I agree with you that publication as an Experimental or Standards 
Track RFC would be suitable for Simple CBA, while the prospective IRTF 
Research Track would be more appropriate for the rest of CBA, IMO.

Regards,
- Christian

-- 
Christian Vogt, Institute of Telematics, Universitaet Karlsruhe (TH)
www.tm.uka.de/~chvogt/pubkey/


Greg Daley wrote:
> Hi,
> 
> I just read the draft of the new CBA, and think it's
> in good shape to progress toward publication.
> It looks like the document has been made
> straightforward and concise.
> 
> What's the plan?
> 
> Is the aim to get it put out as an experimental RFC
> here, or get the document adopted and reviewed in IETF?
> 
> Greg



_______________________________________________
Mobopts mailing list
Mobopts@irtf.org
https://www1.ietf.org/mailman/listinfo/mobopts



From mobopts-bounces@irtf.org Tue Feb 21 02:37:12 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FBS5A-0004GT-EP; Tue, 21 Feb 2006 02:37:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FBS58-0004GF-DL
	for mobopts@irtf.org; Tue, 21 Feb 2006 02:37:10 -0500
Received: from iramx1.ira.uni-karlsruhe.de ([141.3.10.80])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FBS58-0006qb-33
	for mobopts@irtf.org; Tue, 21 Feb 2006 02:37:10 -0500
Received: from i72ms2.tm.uni-karlsruhe.de ([141.3.70.17]
	helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by iramx1.ira.uni-karlsruhe.de with esmtps id 1FBS55-0004Lh-G0
	for <mobopts@irtf.org>; Tue, 21 Feb 2006 08:37:09 +0100
Received: from [IPv6:2001:638:204:6:20c:6eff:fe40:8d95]
	(archimedes.ipv6.tm.uni-karlsruhe.de
	[IPv6:2001:638:204:6:20c:6eff:fe40:8d95])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id 542577E2E
	for <mobopts@irtf.org>; Tue, 21 Feb 2006 08:37:07 +0100 (CET)
Message-ID: <43FAC323.5070704@tm.uka.de>
Date: Tue, 21 Feb 2006 08:37:07 +0100
From: Christian Vogt <chvogt@tm.uka.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE;
	rv:1.7.12) Gecko/20050923 Thunderbird/1.0.7 Mnenhy/0.7.2.0
X-Accept-Language: de-DE, de, en-us, en
MIME-Version: 1.0
To: Mobopts <mobopts@irtf.org>
X-Enigmail-Version: 0.90.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -5.0 (-----)
X-Spam-Status: No
X-Spam-Report: -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP
	-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	-0.6 AWL AWL: From: address is in the auto white-list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Subject: [Mobopts] I-D ACTION:draft-vogt-mobopts-simple-cba-00.txt
X-BeenThere: mobopts@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP Mobility Optimizations <mobopts.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mobopts>,
	<mailto:mobopts-request@irtf.org?subject=unsubscribe>
List-Post: <mailto:mobopts@irtf.org>
List-Help: <mailto:mobopts-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mobopts>,
	<mailto:mobopts-request@irtf.org?subject=subscribe>
Errors-To: mobopts-bounces@irtf.org

Hi everybody,

we submitted a re-written specification of CBA.  This draft is limited 
to the basic CBA mode, where the correspondent node measures a mobile 
node's effort in terms of the packets received from that mobile node.

	Title		: Credit-Based Authorization for Concurrent
                           Reachability Verification
	Author(s)	: C. Vogt, J. Arkko
	Filename	: draft-vogt-mobopts-simple-cba-00.txt
	Pages		: 19
	Date		: 2006-2-15
	
    Mobility and multi-homing protocols enable multi-addressed nodes to
    redirect ongoing communication sessions from one IP address to
    another.  Most of these protocols verify a multi-addressed node's
    reachability at a claimed new IP address in order to prevent
    redirection-based flooding attacks.  In view of reduced protocol
    latencies, such verification is preferably performed concurrently,
    i.e., while packets are already being sent to the new IP address.
    This document defines Credit-Based Authorization, a technique that
    facilitates concurrent reachability verification without compromise
    of security.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-vogt-mobopts-simple-cba-00.txt

Best regards,
- Christian

-- 
Christian Vogt, Institute of Telematics, Universitaet Karlsruhe (TH)
www.tm.uka.de/~chvogt/pubkey/

_______________________________________________
Mobopts mailing list
Mobopts@irtf.org
https://www1.ietf.org/mailman/listinfo/mobopts



From mobopts-bounces@irtf.org Wed Feb 22 20:10:10 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FC4zi-0007Lj-LQ; Wed, 22 Feb 2006 20:10:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FC4zh-0007LV-6I
	for mobopts@irtf.org; Wed, 22 Feb 2006 20:10:09 -0500
Received: from darkstar.iprg.nokia.com ([205.226.5.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FC4zg-0004rU-Mu
	for mobopts@irtf.org; Wed, 22 Feb 2006 20:10:09 -0500
Received: (from root@localhost)
	by darkstar.iprg.nokia.com (8.11.0/8.11.0-DARKSTAR) id k1N0WBN29208
	for <mobopts@irtf.org>; Wed, 22 Feb 2006 16:32:11 -0800
X-mProtect: <200602230032> Nokia Silicon Valley Messaging Protection
Received: from mvdhcp14188.americas.nokia.com (172.18.141.88,
	claiming to be "[127.0.0.1]")
	by darkstar.iprg.nokia.com smtpdpIx1YY; Wed, 22 Feb 2006 16:32:09 PST
Message-ID: <43FD0B61.4040207@iprg.nokia.com>
Date: Wed, 22 Feb 2006 17:09:53 -0800
From: Rajeev Koodli <rajeev@iprg.nokia.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "mobopts@irtf.org" <mobopts@irtf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6
Subject: [Mobopts] New IRTF process for RG RFCs
X-BeenThere: mobopts@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP Mobility Optimizations <mobopts.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mobopts>,
	<mailto:mobopts-request@irtf.org?subject=unsubscribe>
List-Post: <mailto:mobopts@irtf.org>
List-Help: <mailto:mobopts-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mobopts>,
	<mailto:mobopts-request@irtf.org?subject=subscribe>
Errors-To: mobopts-bounces@irtf.org


Folks,

after considerable deliberation, we have a new process which I believe 
will bring a much-needed formal peer review process for RG documents. I 
feel this is very good for us, personally having brought it up many a 
time earlier, including during the IAB review of MobOpts in Paris. So, I 
am looking forward to it.

Please see the process description below. I hope it is encouraging to all!

Regards,

-Rajeev

ps: to begin with, I will act as the shepherd (see below).

...............................................................

- An RG decides to publish a document using the IRTF publication
     track. The RG performs a review for editorial and technical
     content.  The document should have a statement in the abstract
     identifying the document as the product of the RG and a paragraph
     in the first section describing the level of support for the
     document (e.g., "this document represents the consensus of the
     FOOBAR RG", "the views in this document were considered
     controversial by the FOOBAR RG but the RG reached a consensus that
     the document should still be published") and the breadth of review
     for the document.  I.e., was this document read by all the active
     contributors, 3 people, or folks who are not "in" the RG but are
     expert in the area?  It should also be very clear throughout the
     document that it is not an IETF product and is not a standard.  If
     an experimental protocol is described appropriate caveats need to
     be present.

   - Documents should have a shepherd.  This is a relatively new
     concept developed in the IETF to ensure that issues raised in the
     review and publication process (e.g., by the IESG and RFC Editor)
     are responded to in a timely manner.  The IETF shepherding process
     is described in draft-ietf-proto-wgchair-doc-shepherding-05.txt
     and should be adapted to the IRTF publication process as some
     items in the draft will not apply.

   - The sponsoring RG chair brings the document to the IRSG for
     publication.  The expectation is that the RG chair has already
     reviewed the draft thoroughly and considers it of publishable
     quality editorially and technically.  The RG should be copied on
     the mail message requesting IRSG review.

   - A (firm) eight-week IRSG review period follows after which a poll
     is taken.  Reviews should be similar to that for a conference
     paper.  Votes can be:

     = 'ready to publish' -- requires a thorough read and reasonably
       detailed review

     = 'not ready to publish' -- requires a thorough read, reasonably
        detailed review, and actionable comments.

     = 'no objection' -- I don't object if this document goes forward;
       I've read the document (perhaps quickly); I have some small
       comments which are not show stoppers; I don't have great
       expertise in the area.

     = 'request more time to review' -- a commitment to to provide a
       thorough review in a specified period of time.

     Reviews should be written to be public.  In particular, they
     should be sent to the submitted RG mailing list.  (We may need a
     tracker of some sort to collect reviews.)

     At least two other IRSG members (besides the one sponsoring the
     document) need to vote 'ready to publish' for the document to move
     forward.  Any vote of 'not ready to publish' will hold a documents
     progress until the comments are addressed.  The IRTF chair may
     choose to override 'not ready to publish' holds that, in the
     opinion of the chair, have received an adequate response.

   - The document is submitted to the RFC Editor who does not perform
     an ISR review.  The RFC Editor sends it to the IESG for an RFC3932
     review.  There are several reasons why the IESG may block a
     document, described in RFC3932 section 4.  (The document shepherd
     should be responsible for checking the IETF datatracker for IESG
     blocking and non-blocking comments and forward them to the RG.)

   - Rather than the disclaimers found in RFC3932, the IESG will
     instruct the RFC Editor to add the following disclaimer:

       "This RFC is a product of the Internet Research Task Force and
       is not a candidate for any level of Internet Standard.  The IRTF
       publishes the results of Internet-related research and
       development activities.  These results may not be suitable for
       deployment."

     For documents that specify a protocol or other technology, and
     that have been considered in the IETF at one time:

       "This RFC is a product of the Internet Research Task Force.  The
       content of this RFC was at one time considered by the IETF, and
       therefore it may resemble a current IETF work in progress or a
       published IETF work.  However, this is not an IETF document is
       not a candidate for any level of Internet Standard.  The IRTF
       publishes the results of Internet-related research and
       development activities.  These results may not be suitable for
       deployment."

    (These disclaimers will require approval by the IESG.)



_______________________________________________
Mobopts mailing list
Mobopts@irtf.org
https://www1.ietf.org/mailman/listinfo/mobopts



From mobopts-bounces@irtf.org Thu Feb 23 02:57:56 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FCBMK-0008C6-HK; Thu, 23 Feb 2006 02:57:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FCBMJ-0008Bv-4w
	for mobopts@irtf.org; Thu, 23 Feb 2006 02:57:55 -0500
Received: from iramx1.ira.uni-karlsruhe.de ([141.3.10.80])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCBMH-0004ft-RY
	for mobopts@irtf.org; Thu, 23 Feb 2006 02:57:55 -0500
Received: from i72ms2.tm.uni-karlsruhe.de ([141.3.70.17]
	helo=smtp.ipv6.tm.uni-karlsruhe.de)
	by iramx1.ira.uni-karlsruhe.de with esmtps 
	id 1FCBME-0000Pl-97; Thu, 23 Feb 2006 08:57:52 +0100
Received: from [IPv6:2001:638:204:6:20c:6eff:fe40:8d95]
	(archimedes.ipv6.tm.uni-karlsruhe.de
	[IPv6:2001:638:204:6:20c:6eff:fe40:8d95])
	by smtp.ipv6.tm.uni-karlsruhe.de (Postfix) with ESMTP id 118E58541;
	Thu, 23 Feb 2006 08:57:50 +0100 (CET)
Message-ID: <43FD6AFD.1060401@tm.uka.de>
Date: Thu, 23 Feb 2006 08:57:49 +0100
From: Christian Vogt <chvogt@tm.uka.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE;
	rv:1.7.12) Gecko/20050923 Thunderbird/1.0.7 Mnenhy/0.7.2.0
X-Accept-Language: de-DE, de, en-us, en
MIME-Version: 1.0
To: Mobopts <mobopts@irtf.org>
X-Enigmail-Version: 0.90.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: -5.0 (-----)
X-Spam-Status: No
X-Spam-Report: -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP
	-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
	[score: 0.0000]
	-0.6 AWL AWL: From: address is in the auto white-list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: Jari Arkko <jari.arkko@kolumbus.fi>,
	Rajeev Koodli <rajeev.koodli@nokia.com>, William Arbaugh <waa@cs.umd.edu>
Subject: [Mobopts] New Version: draft-irtf-mobopts-ro-enhancements-06.txt
X-BeenThere: mobopts@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP Mobility Optimizations <mobopts.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mobopts>,
	<mailto:mobopts-request@irtf.org?subject=unsubscribe>
List-Post: <mailto:mobopts@irtf.org>
List-Help: <mailto:mobopts-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mobopts>,
	<mailto:mobopts-request@irtf.org?subject=subscribe>
Errors-To: mobopts-bounces@irtf.org

Hi everybody,

draft-irtf-mobopts-ro-enhancements has been resubmitted with some 
additions to the Abstract and Introction sections, reflecting the 
reviews that folks have done.

In addition to the the IETF on-line repositories, where the draft will 
hopefully show up soon, here is a permanent link to the draft:

http://doc.tm.uka.de/2006/draft-irtf-mobopts-ro-enhancements-06.txt

Bye,
- Christian

-- 
Christian Vogt, Institute of Telematics, Universitaet Karlsruhe (TH)
www.tm.uka.de/~chvogt/pubkey/

_______________________________________________
Mobopts mailing list
Mobopts@irtf.org
https://www1.ietf.org/mailman/listinfo/mobopts



