[precis] Mirja Kühlewind's No Objection on draft-ietf-precis-7564bis-08: (with COMMENT)

[Mirja Kühlewind]

Mirja Kühlewind has entered the following ballot position for
draft-ietf-precis-7564bis-08: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-precis-7564bis/



--
COMMENT:
--

not a problem but I noticed that marc is author and shepherd of this document
which looks a bit weird...


___
precis mailing list
precis@ietf.org
https://www.ietf.org/mailman/listinfo/precis

Re: [precis] Gen-art last call review of draft-ietf-precis-7613bis-07

[Linda Dunbar]

Peter, 

Thank you very much for the explanation and the revised wording. Your new 
wording is much clearer and help people to understand why to postpone the 
checking. 

Thank you. 

Linda Dunbar

-Original Message-
From: Peter Saint-Andre - Filament [mailto:pe...@filament.com] 
Sent: Monday, June 26, 2017 8:41 PM
To: Peter Saint-Andre - Filament ; Linda Dunbar 
; gen-...@ietf.org
Cc: precis@ietf.org; i...@ietf.org; draft-ietf-precis-7613...@ietf.org
Subject: Re: [precis] Gen-art last call review of draft-ietf-precis-7613bis-07

On 6/26/17 5:48 PM, Peter Saint-Andre - Filament wrote:
> Hi Linda,
> 
> Thanks for your review. Comments inline.
> 
> On 6/26/17 4:53 PM, Linda Dunbar wrote:
>>  
>> Reviewer: Linda Dunbar
>> Review result: Ready
>>  
>> I am the assigned Gen-ART reviewer for this draft. The General Area 
>> Review Team (Gen-ART) reviews all IETF documents being processed by 
>> the IESG for the IETF Chair.  Please treat these comments just like 
>> any other last call comments.
>>  
>> For more information, please see the FAQ at
>>  
>> .
>>  
>> Document: draft-ietf-precis-7613bis
>> Reviewer: Linda Dunbar
>> Review Date: 2017-06-25
>> IETF LC End Date: 2017-06-27
>> IESG Telechat date: 2017-07-06
>>  
>> Summary:
>> The document is written very clear. Even for a person who is not 
>> familiar with the App area, I can follow through the description. The 
>> document is ready for publication as standard track document Major issues:
>>  
>> One Minor issue:
>>  
>> Page 6 last paragraph has:
>> /SASL mechanisms SHOULD delay any casemapping to the last 
>> possible moment, such as when doing a lookupby username, 
>> performing username comparisons, or generating acryptographic 
>> salt from a username (if the last possible momenthappens on the 
>> server, then decisions about case mapping can be amatter of 
>> deployment policy). In keeping with [RFC4422], SASLmechanisms are 
>> not to apply this or any other profile toauthorization 
>> identifiers, only to authentication identifiers./
>>  
>> What does "last possible moment" mean? When I read it, I thought it 
>> meant wait until you got all the characters. But the next sentence 
>> mentions "..happens on the server". How is the "server" related to 
>> the entity that check the user name & password?
> 
> Many authentication decisions happen on an application server to which 
> a user-oriented client connects (think of an email client connecting 
> to an email server). By "last possible moment" we're referring to 
> processing within the application server or an authentication module 
> thereof - for instance, instead of performing case mapping on first 
> receiving data from the client (thus implying that the case 
> information is lost through most of the processing stages), it's 
> better to lose that information only at the very end. Do you feel it 
> would it help to add a more detailed description of the reasoning here?

Here is a proposed adjustment to the text:

OLD

  SASL mechanisms SHOULD delay any case
  mapping to the last possible moment, such as when doing a lookup
  by username...

NEW

  Because case mapping results in
  information loss, in order to retain that information for as long
  as possible during processing, implementations SHOULD delay any
  case mapping to the last possible moment, such as when doing a
  lookup by username...

Peter

___
precis mailing list
precis@ietf.org
https://www.ietf.org/mailman/listinfo/precis

[precis] version -08 I-Ds

[Peter Saint-Andre]

I've updated the PRECIS bis I-Ds to reflect comments received during
IETF Last Call (including from various directorate reviews).

Peter

___
precis mailing list
precis@ietf.org
https://www.ietf.org/mailman/listinfo/precis

[precis] I-D Action: draft-ietf-precis-7700bis-08.txt

[internet-drafts]

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Preparation and Comparison of 
Internationalized Strings of the IETF.

Title   : Preparation, Enforcement, and Comparison of 
Internationalized Strings Representing Nicknames
Author  : Peter Saint-Andre
Filename: draft-ietf-precis-7700bis-08.txt
Pages   : 11
Date: 2017-06-27

Abstract:
   This document describes methods for handling Unicode strings
   representing memorable, human-friendly names (called "nicknames",
   "display names", or "petnames") for people, devices, accounts,
   websites, and other entities.  This document obsoletes RFC 7700.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-precis-7700bis/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-precis-7700bis-08
https://datatracker.ietf.org/doc/html/draft-ietf-precis-7700bis-08

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-precis-7700bis-08


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

___
precis mailing list
precis@ietf.org
https://www.ietf.org/mailman/listinfo/precis