IETF Logo Mail Archive

[http-auth] Fwd: re-call for IETF http-auth BoF

Yutaka OIWA <y.oiwa@aist.go.jp> Fri, 10 June 2011 02:22 UTC

Return-Path: <yutaka-oiwa-aist-temp@g.oiwa.jp>
X-Original-To: http-auth@ietfa.amsl.com
Delivered-To: http-auth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95B7611E80BA for <http-auth@ietfa.amsl.com>; Thu, 9 Jun 2011 19:22:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level:
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xlfwMg46B08u for <http-auth@ietfa.amsl.com>; Thu, 9 Jun 2011 19:22:54 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id BE6B811E8076 for <http-auth@ietf.org>; Thu, 9 Jun 2011 19:22:53 -0700 (PDT)
Received: by gxk19 with SMTP id 19so1676237gxk.31 for <http-auth@ietf.org>; Thu, 09 Jun 2011 19:22:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.104.3 with SMTP id b3mr2533448ybc.166.1307672573129; Thu, 09 Jun 2011 19:22:53 -0700 (PDT)
Sender: yutaka@g.oiwa.jp
X-Google-Sender-Delegation: yutaka@g.oiwa.jp
Received: by 10.151.103.4 with HTTP; Thu, 9 Jun 2011 19:22:53 -0700 (PDT)
In-Reply-To: <BANLkTinAdEoJNd=5x3ek4+pNF6ZvUrurhA@mail.gmail.com>
References: <878vtgfbs1.fsf@bluewind.rcis.aist.go.jp> <87hb7zdqjo.fsf@bluewind.rcis.aist.go.jp> <4DF0DB72.9090601@gmx.de> <BANLkTinAdEoJNd=5x3ek4+pNF6ZvUrurhA@mail.gmail.com>
Date: Fri, 10 Jun 2011 11:22:53 +0900
X-Google-Sender-Auth: 2BGXD9S7u8fjlqhNvypyYl4u2QE
Message-ID: <BANLkTi=bB-qj=03GB3tr_HboSwD2UB1uVA@mail.gmail.com>
From: Yutaka OIWA <y.oiwa@aist.go.jp>
To: http-auth@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: [http-auth] Fwd: re-call for IETF http-auth BoF
X-BeenThere: http-auth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: HTTP authentication methods <http-auth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/http-auth>, <mailto:http-auth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/http-auth>
List-Post: <mailto:http-auth@ietf.org>
List-Help: <mailto:http-auth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-auth>, <mailto:http-auth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jun 2011 03:17:17 -0000

I forgot to send a reply to the mailing list, so forwarding for your
reference...
Sorry for inconvenience.


---------- Forwarded message ----------
From: Yutaka OIWA <y.oiwa@aist.go.jp>
Date: 2011/6/10
Subject: Re: [http-auth] re-call for IETF http-auth BoF
To: Julian Reschke <julian.reschke@gmx.de>


Dear Julian:

2011/6/9 Julian Reschke <julian.reschke@gmx.de>:
> That's kind of misleading; the core HTTP protocol doesn't define any
> concrete authentication schemes at all; it just offers a framework (header
> fields, status codes etc).

Thank you for comment.  My intention was RFC 2616+2617 as a core,
but the view of your comment seems to be more clear.

> I believe you need to add HTTPbis.

Yes, I'm sorry.


Yutaka

v2.23.0 | Report a Bug | By Email