Is there a reason that this is not doing last call at the same time? Jim
> -----Original Message----- > From: dane [mailto:[email protected]] On Behalf Of Warren Kumari > Sent: Monday, February 23, 2015 9:31 AM > To: <[email protected]> > Subject: Re: [dane] Start of WGLC for draft-ietf-dane-openpgpkey - *please* > review. > > [ Meta top post ] > > I'd like to also draw attention to the "companion" document draft-ietf-dane- > openpgpkey-usage ( http://datatracker.ietf.org/doc/draft-ietf-dane- > openpgpkey-usage/ ), which describes usage of openpgpkey records, and > following CNAMES. > > On Sun, Feb 22, 2015 at 11:08 PM, Viktor Dukhovni <ietf- > [email protected]> wrote: > > On Sun, Feb 22, 2015 at 07:58:19PM -0800, Jim Schaad wrote: > > > >> I am on a case sensitive receiving domain. > >> There are two recipients - JimSch and jimsch on the domain. > >> jimsch has a record but JimSch does not. > >> I now try and send mail to JimSch but get a key for jimsch. > > > > You forgot to hash the tag with the case-folded name. > > > > Speaking of which, IIRC neither the OPENPGPKEY nor the SMIMEA draft > > explicitly mentions what to do about quoted localparts: > > > > "Sam.Jr."@example.com > > > > The localpart is not a dot-atom, and thus requires double-quotes. > > My contention is that in this case the input to SHA2-224 MUST include > > the quotes: > > > > SHA2-224("Sam.Jr.") > > > > not > > > > SHA2-224("Sam.Jr.") > > > > In this case the simplest tagging scheme is: > > > > JimSch - unfolded hash input > > jimsch@lowercase - folded hash input > > > > any email address of the form: > > > > "jimsch@lowercase"@example.com > > > > would be hashed together with the quotes! > > > > I don't have a pointer to my original proposal handy, check the > > archives. It is something along these lines. > > I *think* that the proposal is in this email: > http://www.ietf.org/mail-archive/web/dane/current/msg07163.html > (Viktor, 11 Dec 2014) > > This seemed to be mostly met with acceptance (or, at least closer than many > of the other options!), but didn't address the user+tag@ or > johnsmith=john.smith=jo.hn.sm.th special hanging the gMail does. > A potential, but icky solution to those could be synthesized records. > > I'd just like to note that having a single rule for mapping ascii addresses (e.g > lowercase, s/\.//g, s/\+.*// ) sure would have been nice. Next time > someone has access to a time machine... > > W > > > > > -- > > Viktor. > > > > _______________________________________________ > > dane mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/dane > > > > -- > I don't think the execution is relevant when it was obviously a bad idea in the > first place. > This is like putting rabid weasels in your pants, and later expressing regret at > having chosen those particular rabid weasels and that pair of pants. > ---maf > > _______________________________________________ > dane mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dane _______________________________________________ dane mailing list [email protected] https://www.ietf.org/mailman/listinfo/dane
