Re: [proto-team] Re: Adding IETF tracker support for IAB and IRTF document shepherds

Allison Mankin <mankin@psg.com> Wed, 10 May 2006 15:54 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fdr13-0006yq-KS; Wed, 10 May 2006 11:54:21 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fdr12-0006xq-OE; Wed, 10 May 2006 11:54:20 -0400
Received: from psg.com ([147.28.0.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fdr12-0003Jx-FU; Wed, 10 May 2006 11:54:20 -0400
Received: from localhost ([127.0.0.1] helo=psg.com) by psg.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from <mankin@psg.com>) id 1Fdr11-0008Ar-It; Wed, 10 May 2006 15:54:19 +0000
To: David Meyer <dmm@1-4-5.net>
Subject: Re: [proto-team] Re: Adding IETF tracker support for IAB and IRTF document shepherds
Date: Wed, 10 May 2006 08:54:19 -0700
From: Allison Mankin <mankin@psg.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: rpelletier@isoc.org, iab@iab.org, henrik@levkowetz.com, proto-team@ietf.org
X-BeenThere: proto-team@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Process and Tools Team <proto-team.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/proto-team>, <mailto:proto-team-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:proto-team@ietf.org>
List-Help: <mailto:proto-team-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/proto-team>, <mailto:proto-team-request@ietf.org?subject=subscribe>
Errors-To: proto-team-bounces@ietf.org
Message-Id: <E1Fdr13-0006yq-KS@megatron.ietf.org>

Dave,

You're reading the notation well.  Good catch.  That state
transition is absolutely needed - we just missed putting it in.
We'll update asap in a version d on
http://www1.tools.ietf.org/wg/proto/draft-ietf-proto-iab-irtf-tracker-ext/

Allison

> 
> 
> 	Quick question on section 2.1:
> 
> 	It looks like the only transitions (Possible next states)
> 	available from the "Active IAB Document" state are
> 	"Parked IAB Document", "Dead". Seems like we should be
> 	able to transition to "In IAB Internal Last Call" from
> 	"Active IAB Document". 
>
> 	This is on the theory that a succesful IAB document would
> 	(roughly) follow the following states (with attendant
> 	poor ascii drawing; "permitted substates in the states
> 	following  "Active IAB Document" are shorthand for the
> 	first one; i.e., you can iterate around in the permitted
> 	substates; there are other transitions too, as you note):
> 
> 
>                                              +---------------+
>                                              |               |
>                                             \|/              |
> 	 Active IAB Document --------> permitted substates --+
>                                              |
>                                              |
>                 +----------------------------+
>                 |
>                 |
>                 |
>                \|/                          
>          In IAB Internal Last Call --> permitted substates ---+
>                                                               |
>                 +---------------------------------------------+
>                 |
>                \|/
>          In IAB Community Review   --> permitted substates ---+
>                                                               |
>                 +---------------------------------------------+
>                 |
>                \|/
> 	 RFC Ed Queue
> 
> 
> 
> 	Or am I not understanding the notation used section 2.1?
> 
> 	Thanks,
> 
> 	--dmm
> 
> 

_______________________________________________
proto-team mailing list
proto-team@ietf.org
https://www1.ietf.org/mailman/listinfo/proto-team