Re: FEC ID allocation

Given that this thread is stalling without consensus, I propose to
dismiss the proposal of changing the strategy for allocating FEC
Encoding IDs and sticking with the policy specified in
draft-ietf-rmt-fec-bb-revised-02: "IETF Consensus".
draft-ietf-rmt-fec-bb-revised-02 already went through WG last call
without major revision needed.

If however you have new points to make, please speak now.

	thank you,
	Lorenzo

On Wed, Nov 23, 2005 at 09:47:27AM -0800, Lorenzo Vicisano wrote:
> At the Vancouver meeting we had a discussion on possibly revising the
> strategy for allocating FEC Encoding IDs. The discussion was
> inconclusive and hence it was decided to bring this issue to the list,
> starting a 1-week WG last-call on it.
> 
> The current strategy for allocating FEC Encoding IDs is
> 
>   A) IETF-Consensus, i.e. requiring an IETF RFC that specifies all the
>      requested information (see draft-ietf-rmt-fec-bb-revised-02) and that
>      instructs IANA to assign a specific ID.
> 
> One alternative proposal on the table was to transform IETF consensus into
> 
>   B) Standard Action, i.e. requiring a Standard-Track IESG approved
>      RFC
> 
> Another was:
> 
>   C) IETF-Consensus OR [ Specification-Required AND Expert Review ],
>      i.e. allow also non IETF specification to assign IDs subject to Expert
>      Review.
> 
> I would like to hear any opinion on these options by Wed November 30th.
> Please check the meeting minutes for additional background information.
> 
> Note that the strategy for allocating FEC Instance IDs is "First Come
> First Served" and is not being discussed here.
> 
> 	thank you,
> 	Lorenzo
>      
> 
> _______________________________________________
> Rmt mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/rmt