[AFS3-std] Re: A call for consensus on draft-brashear-afs3-pts-extended-names-07

[Douglas E. Engert]

On 1/6/2011 3:08 PM, Douglas E. Engert wrote:
> Derrick has sent the requested text to the list see below. We need some
> comments from the list, as to OK.

In the view of this chair, we have received many positive comments and
no negative comments on the explanation, and thus the consensus is that
the draft-brashear-afs3-pts-extended-names-07 should be accepted.

The way I am reading draft-wilkinison-afs3-standardisation-00 Section
2.3.3, the pts draft should be moved to experimental, which would require
the author to add the explanation and submit it to the RFC editors
as experimental.

Section 2.3.3 also says: "it needs to be confirmed that the RFC Editor
is happy with this." I propose that we just send it in, and see how it goes.
Anyone got any other in sight into how the editors would handle this? 	

Do we need any additional text saying the afs3-standardization@openafs.org
has consensus for the draft and tat is why it is experimental?


>
> On 1/3/2011 9:22 AM, Derrick Brashear wrote:
>> On Mon, Dec 20, 2010 at 11:45 AM, Douglas E. Engert<deengert@anl.gov> wrote:
>>> The co-chairs have agreed that "implicit mapping" should be explained better
>>> and that after that we could declare the consensus. The discussion about
>>> wild
>>> characters seems to show that there are too many open questions to include
>>> it here. It also is more a question of the implementation because on the
>>> wire
>>> it would not require different RPCs.
>>>
>>> So we need the text for the explanation. I would like to see Derrick as
>>> author, work with Jeff and Andrew (and anyone else with input) to come up
>>> with
>>> the explanation and send to the list for review.
>>
>>
>> An explicit mapping is one that can be configured, represented, and
>> returned by the protocol defined in this document. An implicit mapping
>> is site- or implementation-specific. Examples of implicit mapping would
>> be translation of a client authenticating as Kerberos 5 principal
>> user@REALM to a PTS name of user,
>> and of a client authenticating as Kerberos 5 principal
>> host/sample.host.name@REALM to a PTS name
>> of rcmd.sample, before an AFS ID is looked up and returned.
>> _______________________________________________
>> AFS3-standardization mailing list
>> AFS3-standardization@openafs.org
>> http://lists.openafs.org/mailman/listinfo/afs3-standardization
>>
>>
>

-- 

  Douglas E. Engert  <DEEngert@anl.gov>
  Argonne National Laboratory
  9700 South Cass Avenue
  Argonne, Illinois  60439
  (630) 252-5444