Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Be

ietf

Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice

2014-01-03 06:55:11

On Jan 3, 2014, at 2:36 AM, S Moonesamy <sm+ietf(_at_)elandsys(_dot_)com> wrote:

I'll consider this concern as unresolved.  The Area Directors can review the 
comments and recommend how to resolve the concern.


We are not the Encyclopedia Britannica.   I think Russ' suggestion makes sense.

<Prev in Thread]	Current Thread	[Next in Thread>
Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, S Moonesamy Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, Russ Housley Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, S Moonesamy Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, Ted Lemon <= Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, Randy Bush Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, Sean Turner Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, S Moonesamy Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, Jari Arkko

Previous by Date:	Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, S Moonesamy
Next by Date:	Re: Last Call: <draft-crocker-id-adoption-05.txt> (Creating an IETF Working Group Draft) to Informational RFC, Andrew G. Malis
Previous by Thread:	Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, S Moonesamy
Next by Thread:	Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice, Randy Bush
Indexes:	[Date] [Thread] [Top] [All Lists]