Re: [apps-discuss] The acct: scheme question

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Wed, 23 May 2012 06:43 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0807F21F85B5 for <apps-discuss@ietfa.amsl.com>; Tue, 22 May 2012 23:43:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.714
X-Spam-Level:
X-Spam-Status: No, score=-99.714 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t5lPaJRfzhJv for <apps-discuss@ietfa.amsl.com>; Tue, 22 May 2012 23:43:03 -0700 (PDT)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id 8447721F859B for <apps-discuss@ietf.org>; Tue, 22 May 2012 23:43:01 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id q4N6grgX009628 for <apps-discuss@ietf.org>; Wed, 23 May 2012 15:42:53 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 3038_e50b_85ee0d7c_a4a2_11e1_9be3_001d096c5782; Wed, 23 May 2012 15:42:52 +0900
Received: from [IPv6:::1] ([133.2.210.1]:57400) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S15C8F46> for <apps-discuss@ietf.org> from <duerst@it.aoyama.ac.jp>; Wed, 23 May 2012 15:42:57 +0900
Message-ID: <4FBC86E9.3000906@it.aoyama.ac.jp>
Date: Wed, 23 May 2012 15:42:49 +0900
From: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: John Bradley <ve7jtb@ve7jtb.com>
References: <9452079D1A51524AA5749AD23E00392812B6B6@exch-mbx901.corp.cloudmark.com> <4E1F6AAD24975D4BA5B1680429673943665131A7@TK5EX14MBXC284.redmond.corp.microsoft.com> <7BCF42BF-127F-478B-A922-1E84D087A0F3@ve7jtb.com> <4FBBE0A6.5040906@stpeter.im> <CAC4RtVAD2Q-d-PmM8DjUV=WhdD4Wq_7iteQwrXE2=9B9ryjAUw@mail.gmail.com> <7DC579B3-0B8A-4557-8C16-D2A26E380DF7@cisco.com> <CAA1s49W++e=6cw-2-fDZB7CApaOs_obOwcr7sWJiCyKd9Ttm_g@mail.gmail.com> <1337731132.15399.YahooMailNeo@web31811.mail.mud.yahoo.com> <895C911F-A59C-437C-9DC7-7300D571F8BB@ve7jtb.com>
In-Reply-To: <895C911F-A59C-437C-9DC7-7300D571F8BB@ve7jtb.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: Barry Leiba <barryleiba@computer.org>, "apps-discuss@ietf.org Discuss" <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] The acct: scheme question
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2012 06:43:04 -0000

On 2012/05/23 9:39, John Bradley wrote:
> URN don't have authority portions, so may not be a good fit.
>
> The authority segment is necessary to bootstrap the resolution process.
>
> How about we do the core spec with http://$username@$domain

I have explained earlier that this is not an option. $username is not 
the user *about* which you want information, but the user who *accesses* 
the server.

To give a specific example, if you use an URI such as:

http://john_bradley@www.ietf.org/

then e.g. on Firefox, I get the following message:
    You are about to log in to the site "www.ietf.org" with the username
    "john_bradley", but the website does not require authentication.
    This may be an attempt to trick you.

Under the hood, "john_bradley" is being sent in the relevant http header(s).

Regards,   Martin.

> If we are not intending to have a special protocol handler then http: should work just fine.
>
> The link relationship doesn't need to be a custom scheme.
>
> Whatever Connect references  is going to be around for a long time,  later could be awkward.
>
> John B.
>
> On 2012-05-22, at 7:58 PM, William Mills wrote:
>
>> How about we go with the current draft, and if we hit a significant headwind, we break it out and deal with it separately.
>>
>> If we hit a headwind we couldgo with a few more characters and use urn:acct:$username@$domain. Probably easier to register with IANA a new URN namespace and we're done.
>>
>> -bill
>>
>>
>>
>> From: Bob Wyman<bob@wyman.us>
>> To: Gonzalo Salgueiro<gsalguei@cisco.com>
>> Cc: Barry Leiba<barryleiba@computer.org>; "apps-discuss@ietf.org Discuss"<apps-discuss@ietf.org>
>> Sent: Tuesday, May 22, 2012 4:29 PM
>> Subject: Re: [apps-discuss] The acct: scheme question
>>
>> I would very much prefer that we do NOT create a new WG but rather proceed with acct: as part of WebFinger.
>>
>> WebFinger is designed to work with any URI -- but it needs acct: since what acct: does is not currently done by any other URI scheme.
>>
>> bob wyman
>>
>> On Tue, May 22, 2012 at 6:22 PM, Gonzalo Salgueiro<gsalguei@cisco.com>  wrote:
>>
>> On May 22, 2012, at 3:23 PM, Barry Leiba wrote:
>>
>>>>> I would prefer a separate working group,
>>>>
>>>> Spinning up a working group is a lot of work (writing the charter,
>>>> probably organizing a BoF session at a future IETF meeting, finding
>>>> chairs, etc.). Are you volunteering to help with that? :)
>>>
>>> My sense is that given the discussion so far, we can do this without a
>>> BoF.  And I'm starting to be more and more convinced that we need to
>>> take this out of AppsAWG and give it its own working group (though I'm
>>> not certain of that yet, and I haven't talked with Pete about it).
>>>
>>> That still means we need a draft charter, probably at least a couple
>>> of weeks for discussion and bashing of it, then at least three or four
>>> weeks for the IESG to process it.  Let's say 6 to 8 weeks, if it goes
>>> efficiently and smoothly.  Add time for glitches if they happen.
>>>
>>> If the document can be done in less than, say, 12 to 15 weeks, and if
>>> can get adequate attention, then we should finish it here.  But the
>>> discussion needs to converge.  If it needs more focused attention in
>>> order to converge, then that's a reason to pull it off into a WG of
>>> its own.
>>
>> After having just completed the long drawn out process of authoring a controversial charter that was agreeable to all and finally forming a WG, I would really prefer if we can avoid all that overhead and delay.  We all share the common goal of a robust discovery protocol delivered as expeditiously as possible. I feel we have come a long way given that both camps (SWD and WF) have made concessions and came to an agreeable initial state for a WG draft, along with the maturity of the WF draft and the amount of review and scrutiny it has received from this group I think this is possible if we all remain open-minded and willing to work together.  As far as the acct: URI, I get the sense that most folks don't mind the URI scheme itself. It seems that that the real point of contention is whether it should be split from the original WF doc or not.
>>
>> IMO a strong case can be made for the acct: URI scheme being part of the core WF spec considering the existence of 6415 and its foundational nature for the proposed discovery mechanism and how it is entirely URI driven. Further considering the added work and delay in removing acct: from the current WF spec and how it is already implemented and in the wild,  I'd prefer not to split them at this point. I'm happy to defer to group consensus, though.
>>
>> Cheers,
>>
>> Gonzalo
>>
>>
>>>
>>> Barry
>>> _______________________________________________
>>> apps-discuss mailing list
>>> apps-discuss@ietf.org
>>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>>
>>
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>
>>
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
>>
>>
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
>
>
>
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss