Re: draft-hartman-webauth-phishing-03.txt

To: Eliot Lear <lear at ofcourseimright.com>
Subject: Re: draft-hartman-webauth-phishing-03.txt
From: Sam Hartman <hartmans-ietf at mit.edu>
Date: Wed, 30 May 2007 09:35:10 -0400
Cc: 'IESG' <iesg at ietf.org>, IETF Discussion <ietf at ietf.org>
In-reply-to: <465820C8.3050706@ofcourseimright.com> (Eliot Lear's message of "Sat, 26 May 2007 13:58:00 +0200")
List-help: <mailto:ietf-request@ietf.org?subject=help>
List-id: IETF-Discussion <ietf.ietf.org>
List-post: <mailto:ietf@ietf.org>
List-subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
References: <4656963D.1070702@ofcourseimright.com> <tsltzu03jtw.fsf@mit.edu> <465820C8.3050706@ofcourseimright.com>
User-agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)

I'm at an interop event this week, but I think I now get your concern
with host security and section 4.1 and would like to propose fixes.


Thanks for working with me to understand the concern.

--Sam


_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf

References:
- draft-hartman-webauth-phishing-03.txt
  - From: Eliot Lear
- Re: draft-hartman-webauth-phishing-03.txt
  - From: Sam Hartman
- Re: draft-hartman-webauth-phishing-03.txt
  - From: Eliot Lear

Prev by Date: Re: [Tsvwg] Re: Last Call: draft-ietf-tsvwg-cc-alt (Specifying New Congestion Control Algorithms) to BCP
Next by Date: New IETF Journal available now
Previous by thread: Re: draft-hartman-webauth-phishing-03.txt
Next by thread: Re: Last Call: draft-ietf-hip-dns (Host Identity Protocol (HIP) Domain Name System (DNS) Extensions) to Experimental RFC
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Re: draft-hartman-webauth-phishing-03.txt

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.