From owner-ietf-kink@mail.vpnc.org  Sun Jan  2 16:59:39 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08244
	for <kink-archive@lists.ietf.org>; Sun, 2 Jan 2005 16:59:39 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j02LoJZp062149;
	Sun, 2 Jan 2005 13:50:19 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j02LoJHq062148;
	Sun, 2 Jan 2005 13:50:19 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from cz.mit.edu (STRATTON-FOUR-FORTY-TWO.MIT.EDU [18.187.6.187])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j02LoIWH062131
	for <ietf-kink@vpnc.org>; Sun, 2 Jan 2005 13:50:18 -0800 (PST)
	(envelope-from hartmans@mit.edu)
Received: by cz.mit.edu (Postfix, from userid 8042)
	id 76204E0063; Sun,  2 Jan 2005 16:51:20 -0500 (EST)
To: ietf-kink@vpnc.org
Subject: Moving forward on KINK--deadline for action
From: Sam Hartman <hartmans-ietf@mit.edu>
Message-Id: <20050102215120.76204E0063@cz.mit.edu>
Date: Sun,  2 Jan 2005 16:51:20 -0500 (EST)
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>




Several people have expressed interest in helping with the KINK
effort.  That's great to hear.  It looks like we have or are close to
having sufficient interest to do adequate review.  We also clearly
have interest in implementing the results of the working group.

Assuming fairly dedicated effort, I suspect that we can get the
document into shape within six months and get IESG approval shortly
after that.

I'd like to ask the working group chairs to prepare a new set of
milestones for getting from our current position to a completed
document.  The milestones should include identifying the issues we're
going to fix, coming to consensus on fixes and confirming adequate
review of the result.

Along with the set of milestones, I'llother  need the names of specific
reviewers from the chairs.  I'll need a qualified reviewer for
Kerberos and for IPsec (2401 and IKE).


I expect the results to work will with Kerberos clarifications and
draft-ietf-ipsec-rfc2401bis.

I will have my specific comments on the kink draft to the working
group by January 20; the working group has already received the
general areas I'm concerned about.

In order to set a concrete deadline, I am requesting the milestones
and reviewers from the chairs by February 7, 2005.  I'm picking the
deadline because it is the first scheduling deadline for IETf 62.  If
someone has a preference for another deadline speak up now.  Otherwise
I'll treat February 7 as a hard deadline: if the milestones and
reviewers are submitted by then, we'll continue, but otherwise, the
working group will conclude.

I'd also suggest that KINK consider meeting at IETF 62.  If we can get
enough of the people together it will be useful to discuss the issues
and hopefully come to quick resolution.  Naturally, the decision of
whether to meet is up to the chairs.


Sam Hartman,

Security Area Director



From owner-ietf-kink@mail.vpnc.org  Sun Jan  2 20:20:27 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22818
	for <kink-archive@lists.ietf.org>; Sun, 2 Jan 2005 20:20:25 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j031FF0S022762;
	Sun, 2 Jan 2005 17:15:15 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j031FFsE022757;
	Sun, 2 Jan 2005 17:15:15 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j031FEQL022645
	for <ietf-kink@vpnc.org>; Sun, 2 Jan 2005 17:15:14 -0800 (PST)
	(envelope-from mat@cisco.com)
Received: from sj-core-5.cisco.com (171.71.177.238)
  by sj-iport-3.cisco.com with ESMTP; 02 Jan 2005 18:25:34 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j031FBjw007655;
	Sun, 2 Jan 2005 17:15:11 -0800 (PST)
Received: from thomasm-lnx.cisco.com (thomasm-lnx.cisco.com [171.71.96.50])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j031ChF8001525;
	Sun, 2 Jan 2005 17:12:43 -0800
Subject: Re: Moving forward on KINK--deadline for action
From: Michael Thomas <mat@cisco.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Cc: ietf-kink@vpnc.org
In-Reply-To: <20050102215120.76204E0063@cz.mit.edu>
References: <20050102215120.76204E0063@cz.mit.edu>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-xLf2xNgAoDqMIzCNzLDx"
Organization: Cisco Systems
Message-Id: <1104714910.1148.42.camel@thomasm-lnx.cisco.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 
Date: Sun, 02 Jan 2005 17:15:10 -0800
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1104714763.486491"; x:"432200"; a:"rsa-sha1"; b:"nofws:2902";
	e:"Iw=="; n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"d3Iu4QTd3fX4RmsxWHgGJaXKE7hlM0vd57uIEhDb0nUoXSEXD5UYSCpdUPWqM"
	"OYpG6ikGwZZqcz3pP0MpGUILu7J259C9JzGbMHZoBmMyanBpcjGfyjGMPn1bZ"
	"4YPQWjwLbKOLrGXuQ14zJjwuCBB9O4BtoC5IFzmTgbQ6ZpY6g=";
	c:"Subject: Re: Moving forward on KINK--deadline for action";
	c:"From: Michael Thomas <mat@cisco.com>";
	c:"Date: Sun, 02 Jan 2005 17:15:10 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>



--=-xLf2xNgAoDqMIzCNzLDx
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

I think there's some amount of cart before=20
horse going on here: before we set milestones,
etc, etc, it would be nice to know if there
are actual issues or just another round of
editorial clarifications/nits.

		Mike

On Sun, 2005-01-02 at 13:51, Sam Hartman wrote:
>=20
> Several people have expressed interest in helping with the KINK
> effort.  That's great to hear.  It looks like we have or are close to
> having sufficient interest to do adequate review.  We also clearly
> have interest in implementing the results of the working group.
>=20
> Assuming fairly dedicated effort, I suspect that we can get the
> document into shape within six months and get IESG approval shortly
> after that.
>=20
> I'd like to ask the working group chairs to prepare a new set of
> milestones for getting from our current position to a completed
> document.  The milestones should include identifying the issues we're
> going to fix, coming to consensus on fixes and confirming adequate
> review of the result.
>=20
> Along with the set of milestones, I'llother  need the names of specific
> reviewers from the chairs.  I'll need a qualified reviewer for
> Kerberos and for IPsec (2401 and IKE).
>=20
>=20
> I expect the results to work will with Kerberos clarifications and
> draft-ietf-ipsec-rfc2401bis.
>=20
> I will have my specific comments on the kink draft to the working
> group by January 20; the working group has already received the
> general areas I'm concerned about.
>=20
> In order to set a concrete deadline, I am requesting the milestones
> and reviewers from the chairs by February 7, 2005.  I'm picking the
> deadline because it is the first scheduling deadline for IETf 62.  If
> someone has a preference for another deadline speak up now.  Otherwise
> I'll treat February 7 as a hard deadline: if the milestones and
> reviewers are submitted by then, we'll continue, but otherwise, the
> working group will conclude.
>=20
> I'd also suggest that KINK consider meeting at IETF 62.  If we can get
> enough of the people together it will be useful to discuss the issues
> and hopefully come to quick resolution.  Naturally, the decision of
> whether to meet is up to the chairs.
>=20
>=20
> Sam Hartman,
>=20
> Security Area Director

--=-xLf2xNgAoDqMIzCNzLDx
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iQCVAwUAQdicnbMsDAj/Eq++AQKgOgQAnDTYL7DDZFJ9EG42gTguaIozS1QIMIeQ
ojQtwT6kGm57wk5V1WubXaDon+bh8uwvEv4Kwx2FdLNGELU0LdePle2g/QD8PMZy
Z9Ipa6LSKBytIhonCoMbG0RyTiOTpqgGKNTOyV8ZnSxiarvFZ8vT1REsHkxL7uY2
1mWuiEH/VJ4=
=wM71
-----END PGP SIGNATURE-----

--=-xLf2xNgAoDqMIzCNzLDx--



From owner-ietf-kink@mail.vpnc.org  Sun Jan  2 22:34:00 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA01286
	for <kink-archive@lists.ietf.org>; Sun, 2 Jan 2005 22:33:59 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j033TZ5N004324;
	Sun, 2 Jan 2005 19:29:35 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j033TZli004323;
	Sun, 2 Jan 2005 19:29:35 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from luminous.mit.edu (LUMINOUS.MIT.EDU [18.101.1.61])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j033TZ8a004308
	for <ietf-kink@vpnc.org>; Sun, 2 Jan 2005 19:29:35 -0800 (PST)
	(envelope-from hartmans@mit.edu)
Received: by luminous.mit.edu (Postfix, from userid 1000)
	id 39F8676A69; Sun,  2 Jan 2005 22:29:34 -0500 (EST)
To: Michael Thomas <mat@cisco.com>
Cc: ietf-kink@vpnc.org
Subject: Re: Moving forward on KINK--deadline for action
References: <20050102215120.76204E0063@cz.mit.edu>
	<1104714910.1148.42.camel@thomasm-lnx.cisco.com>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Sun, 02 Jan 2005 22:29:34 -0500
In-Reply-To: <1104714910.1148.42.camel@thomasm-lnx.cisco.com> (Michael
 Thomas's message of "Sun, 02 Jan 2005 17:15:10 -0800")
Message-ID: <87wtuv2ns1.fsf@luminous.mit.edu>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


>>>>> "Michael" == Michael Thomas <mat@cisco.com> writes:

    Michael> I think there's some amount of cart before horse going on
    Michael> here: before we set milestones, etc, etc, it would be
    Michael> nice to know if there are actual issues or just another
    Michael> round of editorial clarifications/nits.

I'm fairly sure there are some real issues; I don't expect it to be
horribly complicated to fix them and I don't know of any issues that I
expect to require difficult consensus calls.  


I definitely do know that I want more review of the document before I
take it back to the IESG.

I said I would provide detailed comments to the WG by January 20.  I
know Ken Raeburn has done a review of the document himself and found
issues similar to those I found; I don't know if he plans to send that
review to the working group.  I'm hoping that others who have tried to
implement the protocol will bring forward at least general information
about their concerns while we're trying to set milestones so that we
can take them into account.

If the chairs believe that my timeline for a decision is too
aggressive I expect them to object.

Keep in mind that setting milestones does not preclude us moving
faster than those milestones.



From owner-ietf-kink@mail.vpnc.org  Mon Jan  3 00:15:12 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06750
	for <kink-archive@lists.ietf.org>; Mon, 3 Jan 2005 00:15:11 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j035AS71028222;
	Sun, 2 Jan 2005 21:10:28 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j035AS86028220;
	Sun, 2 Jan 2005 21:10:28 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from aragorn.bbn.com (aragorn.bbn.com [128.33.0.62])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j035A59D027715;
	Sun, 2 Jan 2005 21:10:07 -0800 (PST)
	(envelope-from kseo@bbn.com)
Received: from [128.89.89.115] (dhcp89-089-115.bbn.com [128.89.89.115])
	by aragorn.bbn.com (8.12.7/8.12.7) with ESMTP id j0359wjf003765;
	Mon, 3 Jan 2005 00:09:58 -0500 (EST)
Mime-Version: 1.0
X-Sender: kseo@po2.bbn.com
Message-Id: <p061005d3bdf24f5d9a23@[128.89.89.115]>
Date: Mon, 3 Jan 2005 00:13:09 -0500
To: ietf-enroll@mit.edu, inch@nic.surfnet.nl, ipsec@ietf.org,
        ipseckey@ietf.org, ipsec-policy@vpnc.org, isms@ietf.org,
        kitten@ietf.org, ietf-kink@vpnc.org, ietf-krb-wg@anl.gov,
        ietf-ltans@imc.org, mobike@machshav.com, msec@securemulticast.org,
        ietf-openpgp@imc.org, pki4ipsec@icsalabs.com, ietf-pkix@imc.org,
        ietf-sacred@imc.org, ietf-sasl@imc.org, ietf-ssh@netbsd.org,
        ietf-smime@imc.org, authtime@nist.gov, syslog-sec@employees.org,
        ietf-tls@lists.certicom.com
From: Karen Seo <kseo@bbn.com>
Subject: 2005 Network and Distributed System Security Symposium (NDSS '05)
Cc: kseo@bbn.com
Content-Type: multipart/alternative; boundary="============_-1107393303==_ma============"
X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang)
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


--============_-1107393303==_ma============
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

   ** My apologies if you receive multiple copies of this message. **

                ANNOUNCING THE INTERNET SOCIETY'S
2005 NETWORK AND DISTRIBUTED SYSTEM SECURITY SYMPOSIUM (NDSS'05)

February 2, 2005 - Pre Conference Workshop
February 3-4, 2005 - Symposium
Catamaran Resort Hotel, San Diego, California
General Chair:  Eric Harder, National Security Agency
Program co-Chairs: Dan Simon, Microsoft Research
		   Dan Boneh, Stanford University

ONLINE INFORMATION AND REGISTRATION: http://www.isoc.org/ndss05/

     The 12th annual NDSS Symposium brings together innovative and
     forward thinking members of the Internet community including
     leading edge security researchers and implementers, globally
     recognized security technology experts, and users from both
     the private and public sectors who design, develop, exploit,
     and deploy the technologies that define network and distributed
     system security.

     NDSS'05 provides a balanced mix of technical papers (with a
     strong emphasis on implementation) that cover new and practical
     approaches to security problems that are endemic to network and
     distributed systems. 

THIS YEAR'S TOPICS INCLUDE:
	* Cryptography in Network Security
	* Denial of Service Attacks,
	* Peer to Peer Approaches
	* Internet Defense
	* Intrusion Detection
	* Platform Security.

FEATURED GUEST SPEAKER:
	* Amit Yoran, who was responsible for coordinating cyber-security
           activities for Homeland Security, will speak on "Security
           Challenges and Opportunities of the Future Enterprise"

PRE CONFERENCE WORKSHOP TOPICS INCLUDE:
	* Security in handling mobility on the internet
	* Security in wireless LANs
	* Security for telephony or voice over IP
	* Trust relations in ad hoc networks
	* Key management strategies to support mobility
	* Security in RFID.
      More information is available at:
         http://www.isoc.org/isoc/conferences/ndss/05/workshop.shtml
      Parties interested in submitting papers should see the above
         web page for directions

REGISTER EARLY FOR BEST PRICING
      Registration for NDSS'05 is now open. Student rates are available
      for both the workshop and symposium. See the web site for more
      information -- http://www.isoc.org/ndss05/  Registration fees:
	*  November 31, 2004-January 10, 2005   $625.
	*  After January 10, 2005               $695.

SPONSORSHIP OPPORTUNITIES AVAILABLE!
      If your organization would like to help support NDSS and gain
      visibility through sponsoring, please contact:
      sponsor-ndss@isoc.org.  Information is also available at   
      http://www.isoc.org/ndss05/


Karen Seo
NDSS'05 Publicity Chair
--============_-1107393303==_ma============
Content-Type: text/html; charset="us-ascii"

<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
 --></style><title>2005 Network and Distributed System Security
Symposium (ND</title></head><body>
<div>&nbsp; ** My apologies if you receive multiple copies of this
message. **</div>
<div><font color="#000000"><br></font></div>
<div><font
color="#000000"
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span
></span>&nbsp;&nbsp;&nbsp; ANNOUNCING THE INTERNET
SOCIETY'S</font></div>
<div><font color="#000000">2005 NETWORK AND DISTRIBUTED SYSTEM
SECURITY SYMPOSIUM (NDSS'05)</font></div>
<div><font color="#000000"><br>
February 2, 2005 - Pre Conference Workshop<br>
February 3-4, 2005 - Symposium<br>
Catamaran Resort Hotel, San Diego, California</font></div>
<div><font color="#000000">General Chair:&nbsp; Eric Harder, National
Security Agency</font></div>
<div><font color="#000000">Program co-Chairs: Dan Simon, Microsoft
Research</font></div>
<div><font
color="#000000"><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>&nbsp;&nbsp; Dan Boneh, Stanford University</font></div>
<div><font color="#000000"><br>
ONLINE INFORMATION AND REGISTRATION: http://www.isoc.org/ndss05/<br>
<br>
&nbsp;&nbsp;&nbsp; The 12th annual NDSS Symposium brings together
innovative and</font></div>
<div><font color="#000000">&nbsp;&nbsp;&nbsp; forward thinking members
of the Internet community including</font></div>
<div><font color="#000000">&nbsp;&nbsp;&nbsp; leading edge security
researchers and implementers, globally</font></div>
<div><font color="#000000">&nbsp;&nbsp;&nbsp; recognized security
technology experts, and users from both</font></div>
<div><font color="#000000">&nbsp;&nbsp;&nbsp; the private and public
sectors who design, develop, exploit,</font></div>
<div><font color="#000000">&nbsp;&nbsp;&nbsp; and deploy the
technologies that define network and distributed</font></div>
<div><font color="#000000">&nbsp;&nbsp;&nbsp; system
security.</font></div>
<div><font color="#000000"><br>
&nbsp;&nbsp;&nbsp; NDSS'05 provides a balanced mix of technical papers
(with a</font></div>
<div><font color="#000000">&nbsp;&nbsp;&nbsp; strong emphasis on
implementation) that cover new and practical</font></div>
<div><font color="#000000">&nbsp;&nbsp;&nbsp; approaches to security
problems that are endemic to network and</font></div>
<div><font color="#000000">&nbsp;&nbsp;&nbsp; distributed
systems.&nbsp;</font></div>
<div><font color="#000000"><br>
THIS YEAR'S TOPICS INCLUDE:<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp; </x-tab>* Cryptography in Network
Security<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </x-tab>* Denial of Service
Attacks,<br>
<x-tab>&nbsp;&nbsp;&nbsp; </x-tab>* Peer to Peer Approaches<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </x-tab>* Internet
Defense<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </x-tab>* Intrusion
Detection<br>
<x-tab>&nbsp;&nbsp; </x-tab>* Platform Security.</font><br>
</div>
<div>FEATURED GUEST SPEAKER:</div>
<div><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </x-tab>* Amit
Yoran, who was responsible for coordinating cyber-security</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; activities
for Homeland Security, will speak on &quot;Security</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Challenges
and Opportunities of the Future Enterprise&quot;</div>
<div><br>
PRE CONFERENCE WORKSHOP TOPICS INCLUDE:<br>
<x-tab> </x-tab>* Security in handling mobility on the internet</div>
<div><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </x-tab>*
Security in wireless LANs<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp; </x-tab>* Security for telephony or
voice over IP<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </x-tab>* Trust relations
in ad hoc networks<br>
<x-tab>&nbsp;&nbsp;&nbsp; </x-tab>* Key management strategies to
support mobility</div>
<div><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </x-tab>*
Security in RFID.</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp; More information is available at:</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
http://www.isoc.org/isoc/conferences/ndss/05/workshop.shtml</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp; Parties interested in submitting papers
should see the above</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; web page for
directions</div>
<div><font color="#000000"><br></font></div>
<div><font color="#000000">REGISTER EARLY FOR BEST
PRICING</font></div>
<div><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp; Registration for
NDSS'05 is now open. Student rates are available</font></div>
<div><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp; for both the
workshop and symposium. See the web site for more</font></div>
<div><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp; information
--&nbsp;</font><font
color="#0000FF"><u>http://www.isoc.org/ndss05/</u></font><font
color="#000000">&nbsp; Registration fees:</font></div>
<div><font
color="#000000"><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>*&nbsp; November 31, 2004-January 10, 2005&nbsp;&nbsp;
$625.</font></div>
<div><font
color="#000000"><x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</x-tab>*&nbsp; After January 10,
2005&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span
></span>&nbsp;&nbsp;&nbsp;&nbsp; $695.</font></div>
<div><font color="#000000"><br>
SPONSORSHIP OPPORTUNITIES AVAILABLE!</font></div>
<div><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp; If your
organization would like to help support NDSS and gain</font></div>
<div><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp; visibility through
sponsoring, please contact:</font></div>
<div><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp;
sponsor-ndss@isoc.org.&nbsp; Information is also available
at&nbsp;&nbsp;&nbsp;</font></div>
<div><font color="#000000">&nbsp;&nbsp;&nbsp;&nbsp;
http://www.isoc.org/ndss05/</font></div>
<div><br></div>
<div><br></div>
<div>Karen Seo</div>
<div>NDSS'05 Publicity Chair</div>
</body>
</html>
--============_-1107393303==_ma============--



From owner-ietf-kink@mail.vpnc.org  Mon Jan  3 00:24:30 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07201
	for <kink-archive@lists.ietf.org>; Mon, 3 Jan 2005 00:24:30 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j035M2lu037012;
	Sun, 2 Jan 2005 21:22:02 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j035M2u7037011;
	Sun, 2 Jan 2005 21:22:02 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from biscayne-one-station.mit.edu (BISCAYNE-ONE-STATION.MIT.EDU [18.7.7.80])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j035M1SB037005
	for <ietf-kink@vpnc.org>; Sun, 2 Jan 2005 21:22:01 -0800 (PST)
	(envelope-from raeburn@MIT.EDU)
Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103])
	by biscayne-one-station.mit.edu (8.12.4/8.9.2) with ESMTP id j035K4Fw004824
	for <ietf-kink@vpnc.org>; Mon, 3 Jan 2005 00:20:04 -0500 (EST)
Received: from [18.101.0.226] ([18.101.0.226])
	(authenticated bits=0)
        (User authenticated as raeburn@ATHENA.MIT.EDU)
	by outgoing.mit.edu (8.12.4/8.12.4) with ESMTP id j035K12d000246
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT)
	for <ietf-kink@vpnc.org>; Mon, 3 Jan 2005 00:20:02 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <87wtuv2ns1.fsf@luminous.mit.edu>
References: <20050102215120.76204E0063@cz.mit.edu> <1104714910.1148.42.camel@thomasm-lnx.cisco.com> <87wtuv2ns1.fsf@luminous.mit.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <1DDD0501-5D47-11D9-AEFF-000A95909EE2@mit.edu>
Content-Transfer-Encoding: 7bit
From: Ken Raeburn <raeburn@MIT.EDU>
Subject: Re: Moving forward on KINK--deadline for action
Date: Mon, 3 Jan 2005 00:20:00 -0500
To: ietf-kink@vpnc.org
X-Mailer: Apple Mail (2.619)
X-Spam-Score: -4.9
X-Spam-Flag: NO
X-Scanned-By: MIMEDefang 2.42
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


On Jan 2, 2005, at 22:29, Sam Hartman wrote:
> I said I would provide detailed comments to the WG by January 20.  I
> know Ken Raeburn has done a review of the document himself and found
> issues similar to those I found; I don't know if he plans to send that
> review to the working group.

Yes, I'll get back to this after finishing my "48 hours" on a couple of 
Kerberos RFCs.

I've only a few comments on the technical stuff so far:

1) Needs alignment with current Kerberos specs.  Forget RFC 1510, use 
kcrypto and clarifications.  In particular, (1) treat "encryption with 
integrity protection" output as a whole, don't peek under the covers to 
find a "checksum" part you can throw away, (2) let kcrypto specify how 
to verify a checksum, as they're not required to be deterministic, so 
the "compute it again and compare" approach specified in section 5 is 
wrong, (3) drop references to the initialization vector, (4) use a prf 
from kcrypto, don't assume the checksum operations are deterministic 
hash functions, (5) a key's encryption type does not directly indicate 
a checksum type, it indicates an encryption(-with-integrity-protection) 
scheme, which does include a required-to-implement checksum type.  
Also, I'd have to go back and check, but I don't think we require that 
a given checksum type have a fixed output size, so "leave X amount of 
space and fill it with zero for computing the checksum" is questionable 
too.

2) More examination of user-to-user case, especially situations where 
it might *not* be two PKINIT clients, which section 3 says is possible. 
  (BTW, in the Kerberos docs, it's "user-to-user", not "user-user".)

3) Verifying remotely supplied identity, as Sam raised earlier.

4) Sec 5, diagram indicates one octet for cksumlen, but the text (and 
kcrypto specifications) say it should be two.

5) Are subsession keys ignored?

6) In the user-to-user case with TGTs, I think the KINK draft may be 
over-specifying things that should be dealt with at the Kerberos level. 
  If things are underspecified in Kerberos Clarifications, let's deal 
with that.

7) Sec 7.1, the time difference MUST be computed and SHOULD be stored 
and used?  Why the different requirement levels?  (And is this sort of 
thing in the domain of KINK or Kerberos?)

8) Sec 6.8: "Kerberos in general does not provide FPS so it is somewhat 
questionable whether a system which is heavily relying on Kerberos 
benefits from PFS."  First, that sounds like it might be Security 
Considerations material.  Second, I don't follow; explain please?

9) Sec 4.3 and 7.3 use SHOULD and MUST respectively regarding when the 
nonce should be used.  If the circumstances they're describing are 
different, that's okay, but if so, I missed it on first reading.

I can throw out some additional editorial comments though:

1) Review the I-D nits and RFC authors docs.  I spotted a lot of 
mechanical things (number of lines per page; avoid hyphenation; use 
ragged right margin; need two spaces after sentence-ending period; fix 
page numbers in table of contents; add section numbers to TOC) most of 
which I think are specified in one of those documents.

2) The reference to [PKCROSS] is unnecessary, and only happens once, in 
the introduction.  I'd suggest dropping it.  That's one less 
unpublished I-D in the references section.

3) Spelling.  "loose" was used where "lose" should've been in at least 
one place, 6.1 says "optmistic" (but hyphenated); 7.3 says "IPspec".  
"'s" is used in some places where I'd use "s" for a plural form.

4) IANA considerations.  I think the correct terminology is "port 
number", not "port", and they're "assigned", not "created".  This 
section says no new registries are required in the first paragraph, and 
the third one specifies that IANA must create one (but without the 
associated procedural data that is required nowadays).  Are the KINK 
payload types and ISAKMP payload types actually ever used in the same 
field?  If not, I don't think they need to come out of the same 
registry.

5) Section 2, last paragraph.  "Between" is generally non-directional, 
but in this case, a direction seems to be intended to be inferred; try 
"from...to" instead.

6) Section 4.3, discussing attributes, mixes singular and plural 
indications.  The word "lone" appears to be popular with the author, 
too. :-)

7) Sect 5.1.1, first item in the list, should end with a period like 
the others.

8) [KRBREVS] is referenced but not listed in the references section.

9) Sec 5.1.7, next to last paragraph on page 21, is "IKE" (the 
protocol) fuzzy about use of different SAs, or is it "[IKE]" (the 
document)?

10) Sec 8: "By optional, it is meant..." is badly worded.

Like I said, I'll try to get back to this soon.

> Along with the set of milestones, I'llother  need the names of specific
> reviewers from the chairs.  I'll need a qualified reviewer for
> Kerberos and for IPsec (2401 and IKE).

I'd be happy to act as a reviewer for the Kerberos aspects, though the 
fact that the document seems to be written to an audience that 
understands IPsec and might need to have Kerberos explained rather than 
the other way around will make it slow going.  Reviewers well versed in 
both protocols would be even better.

Ken



From owner-ietf-kink@mail.vpnc.org  Tue Jan  4 15:25:13 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15442
	for <kink-archive@lists.ietf.org>; Tue, 4 Jan 2005 15:25:12 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j04KAUZG077674;
	Tue, 4 Jan 2005 12:10:30 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j04KAUU7077672;
	Tue, 4 Jan 2005 12:10:30 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from cz.mit.edu (STRATTON-FOUR-FORTY-TWO.MIT.EDU [18.187.6.187])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j04KATNP077650
	for <ietf-kink@vpnc.org>; Tue, 4 Jan 2005 12:10:29 -0800 (PST)
	(envelope-from hartmans@mit.edu)
Received: by cz.mit.edu (Postfix, from userid 8042)
	id E4535E0063; Tue,  4 Jan 2005 15:11:35 -0500 (EST)
To: ietf-kink@vpnc.org
Subject: KINK and RFC2401bis
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Tue, 04 Jan 2005 15:11:35 -0500
Message-ID: <tslvfadkl8o.fsf@cz.mit.edu>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>




I finished reading over RFC 2401bis this morning.  By the time Kink
makes its way to the IESG, it will need to normatively reference that
document instead of RFC 2401.

The primary change is that several of the comments about the SPD
actually apply to the PAD in the 2041bis model.



There's another issue the working group needs to consider.  RFC
2401bis increases the flexibility and requirements for IPsec.  New
requirements include the ability to have multiple SAs with the same
selectors and to have port ranges in selectors.  IKEv1 which Kink is
based on does not support these features.

I'm concerned that people will expect to be able to set up SPD entries
taking advantage of such features and have them work.  I'm asking the
working group to seriously consider whether support for new IPsec
requirements should be added to Kink.  The result of this
consideration needs to be either modifications to the protocol to add
the necessary support or text explaining what features are not
supported and why the working group has chosen not to support them.

--Sam



From owner-ietf-kink@mail.vpnc.org  Tue Jan  4 16:27:44 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24066
	for <kink-archive@lists.ietf.org>; Tue, 4 Jan 2005 16:27:43 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j04LJsZJ052545;
	Tue, 4 Jan 2005 13:19:54 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j04LJsPK052544;
	Tue, 4 Jan 2005 13:19:54 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from sj-iport-1.cisco.com (sj-iport-1-in.cisco.com [171.71.176.70])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j04LJsMn052490
	for <ietf-kink@vpnc.org>; Tue, 4 Jan 2005 13:19:54 -0800 (PST)
	(envelope-from mat@cisco.com)
Received: from sj-core-1.cisco.com (171.71.177.237)
  by sj-iport-1.cisco.com with ESMTP; 04 Jan 2005 13:29:18 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j04LJkvl024885;
	Tue, 4 Jan 2005 13:19:46 -0800 (PST)
Received: from thomasm-lnx.cisco.com (thomasm-lnx.cisco.com [171.71.96.50])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j04LHF46014987;
	Tue, 4 Jan 2005 13:17:15 -0800
Subject: Re: KINK and RFC2401bis
From: Michael Thomas <mat@cisco.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Cc: ietf-kink@vpnc.org
In-Reply-To: <tslvfadkl8o.fsf@cz.mit.edu>
References: <tslvfadkl8o.fsf@cz.mit.edu>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-9316VohwfHyFMn4niaPC"
Organization: Cisco Systems
Message-Id: <1104873588.26508.3.camel@thomasm-lnx.cisco.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 
Date: Tue, 04 Jan 2005 13:19:48 -0800
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1104873435.230866"; x:"432200"; a:"rsa-sha1"; b:"nofws:2264";
	e:"Iw=="; n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw"
	"eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU"
	"tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"Km7XQ624F48WfMYPlRCUt/8CawIrqFFPVdMWTTLKaC4ZKsyVT5WdeFLcp/tS3"
	"DlU0jTart9Rws++LurYfXY3dj6okYb7FIO4bYJSHNSOANiWMTcaktzWZH5AnD"
	"O1I9ZVNO7bSkVPNo1K0RcYR05oTYBrNzc9QDULKYbj0aV8oCk=";
	c:"Subject: Re: KINK and RFC2401bis";
	c:"From: Michael Thomas <mat@cisco.com>";
	c:"Date: Tue, 04 Jan 2005 13:19:48 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>



--=-9316VohwfHyFMn4niaPC
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

I'm fairly certain that the main difference required of
KINK is to change the normative reference from IKEv1 to
IKEv2 for ISAKMP payloads. KINK doesn't do anything with
the payloads themselves, though there may be some error
code differences if my foggy memory on this subject=20
serves me. When I coded this up with the Pluto sources
for IKEv1, I didn't have to change any of the internal
SA establishment/destruction code at all.


		Mike

On Tue, 2005-01-04 at 12:11, Sam Hartman wrote:
>=20
> I finished reading over RFC 2401bis this morning.  By the time Kink
> makes its way to the IESG, it will need to normatively reference that
> document instead of RFC 2401.
>=20
> The primary change is that several of the comments about the SPD
> actually apply to the PAD in the 2041bis model.
>=20
>=20
>=20
> There's another issue the working group needs to consider.  RFC
> 2401bis increases the flexibility and requirements for IPsec.  New
> requirements include the ability to have multiple SAs with the same
> selectors and to have port ranges in selectors.  IKEv1 which Kink is
> based on does not support these features.
>=20
> I'm concerned that people will expect to be able to set up SPD entries
> taking advantage of such features and have them work.  I'm asking the
> working group to seriously consider whether support for new IPsec
> requirements should be added to Kink.  The result of this
> consideration needs to be either modifications to the protocol to add
> the necessary support or text explaining what features are not
> supported and why the working group has chosen not to support them.
>=20
> --Sam

--=-9316VohwfHyFMn4niaPC
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iQCVAwUAQdsIdLMsDAj/Eq++AQK1DQP/fQdUzKHsdczDptpenOyddXs/nbaoX+f9
iNgZpeIi99WOwNjaxNxkuZ2eoM7gIl/VZPGHqRR7VrjBo0BmUJCwtoHsQvDbqWld
gSSOp0beXb2PnT8jALYDLFC8LpQJnzqNfxO0bxBJaKQ8vIiParU59FrpQIMd/azU
9BWR9gcyfT8=
=dDMI
-----END PGP SIGNATURE-----

--=-9316VohwfHyFMn4niaPC--



From owner-ietf-kink@mail.vpnc.org  Tue Jan  4 21:27:55 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14469
	for <kink-archive@lists.ietf.org>; Tue, 4 Jan 2005 21:27:54 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j052KweS034619;
	Tue, 4 Jan 2005 18:20:58 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j052Kwqf034618;
	Tue, 4 Jan 2005 18:20:58 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from march.taca.jp (vbox.nezu.wide.ad.jp [203.178.142.195])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j052Kvfw033925
	for <ietf-kink@vpnc.org>; Tue, 4 Jan 2005 18:20:57 -0800 (PST)
	(envelope-from nov@tahi.org)
Received: from localhost (vbox.nezu.wide.ad.jp [203.178.142.195])
	by march.taca.jp (Postfix) with ESMTP
	id 1FB401FB7D; Wed,  5 Jan 2005 11:20:36 +0900 (JST)
Date: Wed, 05 Jan 2005 11:20:33 +0900 (JST)
Message-Id: <20050105.112033.31815015.nov@tahi.org>
To: hartmans-ietf@mit.edu
Cc: ietf-kink@vpnc.org
Subject: Re: Moving forward on KINK--deadline for action
From: Nobuo OKABE <nov@tahi.org>
In-Reply-To: <20050102215120.76204E0063@cz.mit.edu>
References: <20050102215120.76204E0063@cz.mit.edu>
X-Mailer: Mew version 4.1 on Emacs 20.7 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


From: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Moving forward on KINK--deadline for action
Date: Sun,  2 Jan 2005 16:51:20 -0500 (EST)

> In order to set a concrete deadline, I am requesting the milestones
> and reviewers from the chairs by February 7, 2005.  I'm picking the
> deadline because it is the first scheduling deadline for IETf 62.  If
> someone has a preference for another deadline speak up now.  Otherwise
> I'll treat February 7 as a hard deadline: if the milestones and
> reviewers are submitted by then, we'll continue, but otherwise, the
> working group will conclude.

If fixing new milestones
we will have to estimate the effort which should be
needed for fixing the ID.
So our group is going to show comments as Ken did.
But please wait for a while because it is new-year-holidays
in Japan now :-)

----- nobuo



From owner-ietf-kink@mail.vpnc.org  Tue Jan  4 21:33:25 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14942
	for <kink-archive@lists.ietf.org>; Tue, 4 Jan 2005 21:33:24 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j052VSQ6045260;
	Tue, 4 Jan 2005 18:31:28 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j052VSvs045259;
	Tue, 4 Jan 2005 18:31:28 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from march.taca.jp (vbox.nezu.wide.ad.jp [203.178.142.195])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j052VRV0045250
	for <ietf-kink@vpnc.org>; Tue, 4 Jan 2005 18:31:27 -0800 (PST)
	(envelope-from nov@tahi.org)
Received: from localhost (vbox.nezu.wide.ad.jp [203.178.142.195])
	by march.taca.jp (Postfix) with ESMTP
	id 27EE81FBC2; Wed,  5 Jan 2005 11:31:33 +0900 (JST)
Date: Wed, 05 Jan 2005 11:31:33 +0900 (JST)
Message-Id: <20050105.113133.120215999.nov@tahi.org>
To: inoue@isl.rdc.toshiba.co.jp
Cc: hartmans-ietf@mit.edu, ietf-kink@vpnc.org
Subject: Re: Sufficient Energy to finish KINK--comments by 2005-01-06
From: Nobuo OKABE <nov@tahi.org>
In-Reply-To: <20041231161309.414A215218@shuttle.wide.toshiba.co.jp>
References: <tslk6rgtte3.fsf@cz.mit.edu>
	<20041230.141334.08619128.nov@tahi.org>
	<20041231161309.414A215218@shuttle.wide.toshiba.co.jp>
X-Mailer: Mew version 4.1 on Emacs 20.7 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


From: Atsushi Inoue <inoue@isl.rdc.toshiba.co.jp>
Subject: Re: Sufficient Energy to finish KINK--comments by 2005-01-06
Date: Sat, 01 Jan 2005 01:13:10 +0900

> Because these two groups has experience on implementing and using 
> KINK, we can call for reviewer of KINK draft in these groups.
> Also, we have aready itemize several issues in implementing KINK, we 
> (maybe Kamada-san and some other guys) will write individual I-D on 
> this implementation issue soon. I think this I-D will be a good start 
> point for discussing how to do on KINK work. How about that ?

As considering the deadline Sam has presented,
we should throw our brief version to the ML
before submitting the ID.
It can help the chairs for making new milestones.

----- nobuo



From owner-ietf-kink@mail.vpnc.org  Wed Jan 12 02:20:06 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA04906
	for <kink-archive@lists.ietf.org>; Wed, 12 Jan 2005 02:20:03 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0C7DaMN069232;
	Tue, 11 Jan 2005 23:13:36 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0C7DaCB069229;
	Tue, 11 Jan 2005 23:13:36 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from nasten.nanohz.org (usen-220x218x5x242.ap-US00.usen.ad.jp [220.218.5.242])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0C7DZa5068931
	for <ietf-kink@vpnc.org>; Tue, 11 Jan 2005 23:13:35 -0800 (PST)
	(envelope-from kamada@nanohz.org)
Received: from nasten.nanohz.org (localhost [127.0.0.1])
	by nasten.nanohz.org (Postfix) with ESMTP id 288C911
	for <ietf-kink@vpnc.org>; Wed, 12 Jan 2005 16:13:33 +0900 (JST)
Received: from mitana.nanohz.org ([2001:240:2:0:202:8aff:fefa:bec0])
	by nasten.nanohz.org (smtpsugar 1.1) with ESMTPA
	id 3nqr4h; Wed, 12 Jan 2005 16:13:33 +0900 (JST)
Date: Wed, 12 Jan 2005 16:14:13 +0900
Message-ID: <20050112161413IL%kamada@nanohz.org>
From: "KAMADA Ken'ichi" <kamada@nanohz.org>
To: ietf-kink@vpnc.org
Subject: KINK comments
User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.3.50
 (i386-unknown-netbsdelf2.0G) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


Here is my comments for KINK.
I'd also like to act a reviewer.

Please note that I'm not a Kerberos expert and there may be
some misunderstandings.


1) Sec 8 says "prf is the same hash algorithm found in the session ticket's
etype", but krb-wg-crypto-07 defines hash as unkeyed.
Fortunately krb-wg-crypto-07 defines a PRF for each etype, so KINK
should use this PRF.


2) The format of the encrypted part of KINK_ENCRYPT (Sec 5.1.8) is
vague.  I think of using the output of raw encryption algorithms or
using EncryptedData.

case A)
  I have interpreted the format as the output of encryption algorithms.
  In the word of krb-wg-crypto, E(confounder | plaintext | pad).
  krb-wg-crypto seems to have at least two different types of encryption
  functions.  One is des-cbc-* which places unkeyed checksum in the
  input of encryption, and another is one using simplified profile
  which places HMAC after the output of encryption.
  In either case, when we exclude a checksum from their formats,
  the result is E(confounder | plaintext | pad).

  I think case A is the original author's idea.

case B)
  Some people seem to have interpreted it as EncryptedData.
  If this is the way to go, I agree that it should not be
  decomposed.


3) Sec 7.1 says the checksum in the KRB-ERROR message is not used,
but Sec 5.1.4 says that KINK implementation MUST make use of
keyed Kerberos errors.  But KRB-ERROR does not have checksum in it (at
least with RFC 1510 or kerberos-clarifications).
I think a correct phrase here is "KINK implementations MUST make use of
a KINK Cksum field when returning KINK_KRB_ERROR and the appropriate
service key is available."


4) This may be a naive question but
is there any situation that one host acts as two different
principal in one realm?
If there is, should KINK_TGT_REQ contain principal name (not only
realm name)?


5) With regard to server principal authentication problem in
user-to-user mode which Mr. Hartman noted,
doesn't the KDC check the sname in the TGS_REQ with one in the
additional-ticket when the ENC-TKT-IN-SKEY option is specified?
If it does, I think there is no problem because the client
must know in advance the principal name which she would like
to talk with.  Otherwise, returned principal name or TGT in
the KINK_TGT_REP must be indeed authenticated but I have no idea
for how.


6) Mr. Raeburn said that Kerberos checksum does not necessarily
requires fixed checksum size.  If that is the case and KINK should
support such checksums, the KINK packet format should be changed and
the comments below may be useless.

Kerberos checksum is not deterministic as already pointed out.
The spec should describe how to verify checksum as follows.

To verify the checksum, the checksum is saved, and the
checksum field is zeroed out.  The resulting message and the saved
checksum are passed to the verification function.  If the verification
fails, the message MUST be dropped.


7) If KINK also supports IKEv2 features, at least the following items
should be considered.

- IKEv2 does not have DOI, so how to handle the DOI field in the KINK
  packet header should be described.
- Use TS (Traffic Selector) instead of ID (Identification).
- KEYMAT calculation is changed.
- How to handle REKEY_SA Notify type.


8) In implementor's point of view, I'd like to see initiator's
behavior in receiving KINK_ERROR to be defined.
For example:
- When KINK_OK is received, initiator MAY act as if the KINK_ERROR
  payload was not included in the messaged.
- When KINK_BADQMVERS is received and the Cksum is verified,
  initiator MAY retry in other Quick Mode version.
- When one of other error codes is received and the Cksum is verified,
  initiator SHOULD abort the negotiation.

Honestly, behavior against KINK_KRB_ERROR is welcome, but
it is the scope of Kerberos document (not KINK) so I don't insist on
including it in KINK.


Regards,
-- 
KAMADA Ken'ichi <kamada@nanohz.org>



From owner-ietf-kink@mail.vpnc.org  Tue Jan 18 17:38:36 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13722
	for <kink-archive@lists.ietf.org>; Tue, 18 Jan 2005 17:38:35 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0IMVQaB042828;
	Tue, 18 Jan 2005 14:31:26 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0IMVQaZ042827;
	Tue, 18 Jan 2005 14:31:26 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from cz.mit.edu (CARTER-ZIMMERMAN.MIT.EDU [18.18.3.197])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0IMVPOA042795
	for <ietf-kink@vpnc.org>; Tue, 18 Jan 2005 14:31:25 -0800 (PST)
	(envelope-from hartmans@mit.edu)
Received: by cz.mit.edu (Postfix, from userid 8042)
	id 46BEEE0063; Tue, 18 Jan 2005 17:31:08 -0500 (EST)
To: ietf-kink@vpnc.org
Subject:  AD review: draft-ietf-kink-kink [section 1-4]
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Tue, 18 Jan 2005 17:31:08 -0500
Message-ID: <tslzmz65pzn.fsf@cz.mit.edu>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>



I can tell already that I'm not going to finish up my comments by
Thursday.  My day job has decided to reorganize and this week's IESG
telechat has some documents that are taking me a wihle to go through.
I will get the rest of my comments to the group by early next week

The bad news is that most of the interesting comments I have are in
the second half of the document so this message is not all that
useful.



I'd recommend reading draft-ietf-ipsec-rfc2401bis,
draft-ietf-krb-wg-crypto and skimming
draft-ietf-krb-wg-kerberos-clarifications.

Rfc2401bis is setting before the IESG; there are some discusses
although I expect the document to be approved by IETF 62.

The Kerberos documents have been approved and are in the RFC editor
queue.  The crypto document is actually in auth48 waiting for Ken to
confirm some final edits.



[**] Indicates an issue that I consider substantive and that will
require wg consensus.

First. the document needs to meet all the ID nits when it is
submitted.

Section 1:

Remove the reference to pkcross or cite something outside the IETF.
It's an expired ID without and active editor.

Add an informative reference to IKE.
Section 2:

Kerberos is now using the term user-user rather than user-to-user.


Principals are not either client or service principals; they can and often do fill both roles.

Cite a reference for DER.

Section 3:

English usage/grammar problems with the first two paragraphs.

     which allows a final acknowledgment message when the respondent needs
        a full three-way handshake. This is only needed when the optimistic
           keying route is not taken, though it is expected that that will not
              be the norm. KINK also provides rekeying and dead peer detection as

What is expected not to be the norm?  Please reword.


Section 4.2:

[**] How will the initiator determine whether it will be able to get a
TGT?  I think policy considerations of when to use u2u and
authorization considerations of what u2u principals are authorized are
underspecified in the draft.

[**] Make sure the descriptions of u2u work correctly in the cross-realm case.


Section 4.3:

[**] I need explicit review from the IPsec reviewer of this section to
make sure it is compatible with 2401bis.  IN addition, any differences
between how this works and how IKE would set up the same SA need to be
called out.  It is fine for there to be differences, but I want to
make sure the working group explicitly decided the differences are a
good thing.


I'm somewhat concerned that 4.3 is not specific enough to describe
exactly what key gets set up.  I.E. I'm concerned it may not be
detailed enough for interoperable implementations.


Section 4.4

IPsec does not allow half-open security associations any more as far
as I can tell in 2401bis.  So it's not just for simplicity, but for
model conformance.

Section 4.4.1:

Please make sure this discussion is aligned with 2401bis.  I think it
may change small details but they seem to have adopted much of the
same strategy kink uses.  The area wher I believe they speak to this
issue is when you should rekey (timers etc)
Section 4.4.2

[**] Discuss status message, rebooting peers and u2u.  This looks a
lot like the IKE case where you lose all cryptographic context to me.




From owner-ietf-kink@mail.vpnc.org  Wed Jan 19 20:16:55 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15898
	for <kink-archive@lists.ietf.org>; Wed, 19 Jan 2005 20:16:53 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K16M1F031095;
	Wed, 19 Jan 2005 17:06:22 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0K16M2E031093;
	Wed, 19 Jan 2005 17:06:22 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from miyazawa.org (usen-221x116x13x66.ap-US01.usen.ad.jp [221.116.13.66])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K16Ktf030072
	for <ietf-kink@vpnc.org>; Wed, 19 Jan 2005 17:06:21 -0800 (PST)
	(envelope-from kazunori@miyazawa.org)
Received: from [IPv6:2001:240:2:0:c926:991b:c386:a4d7] ([2001:240:2:0:c926:991b:c386:a4d7])
  (AUTH: LOGIN kazunori, SSL: TLSv1/SSLv3,128bits,RC4-MD5)
  by miyazawa.org with esmtp; Thu, 20 Jan 2005 09:59:34 +0900
  id 000008FF.41EF0276.00006F5F
Message-ID: <41EF03C7.90609@miyazawa.org>
Date: Thu, 20 Jan 2005 10:05:11 +0900
From: Kazunori Miyazawa <kazunori@miyazawa.org>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Michael Thomas <mat@cisco.com>
CC: Sam Hartman <hartmans-ietf@mit.edu>, ietf-kink@vpnc.org
Subject: Re: KINK and RFC2401bis
References: <tslvfadkl8o.fsf@cz.mit.edu> <1104873588.26508.3.camel@thomasm-lnx.cisco.com>
In-Reply-To: <1104873588.26508.3.camel@thomasm-lnx.cisco.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


Hello,

I'm Kazunori Miyazawa. I'm implementing KINK into a small embedded device.

I agree with Mr. Tomas. KINK does not specifiy its payload about IPsec SA
and relegates it to ISAKMP so that the conformity to rfc2401bis depends
on how ISAKMP conforms rfc2401bis.

I think changing the reference from IKEv1 to IKEv2 needs to many
revises on the draft because IKEv2 does not have the phases. If the draft
referencig IKEv2, I guess KINK uses CREATE_CHILD_SA exchange instead of ISAKMP
quick mode. If we only reuse each IKEv2 payload format, we need more definition
in section 7.


Michael Thomas wrote:
> I'm fairly certain that the main difference required of
> KINK is to change the normative reference from IKEv1 to
> IKEv2 for ISAKMP payloads. KINK doesn't do anything with
> the payloads themselves, though there may be some error
> code differences if my foggy memory on this subject 
> serves me. When I coded this up with the Pluto sources
> for IKEv1, I didn't have to change any of the internal
> SA establishment/destruction code at all.
> 
> 
> 		Mike
> 
> On Tue, 2005-01-04 at 12:11, Sam Hartman wrote:
> 
>>I finished reading over RFC 2401bis this morning.  By the time Kink
>>makes its way to the IESG, it will need to normatively reference that
>>document instead of RFC 2401.
>>
>>The primary change is that several of the comments about the SPD
>>actually apply to the PAD in the 2041bis model.
>>
>>
>>
>>There's another issue the working group needs to consider.  RFC
>>2401bis increases the flexibility and requirements for IPsec.  New
>>requirements include the ability to have multiple SAs with the same
>>selectors and to have port ranges in selectors.  IKEv1 which Kink is
>>based on does not support these features.
>>
>>I'm concerned that people will expect to be able to set up SPD entries
>>taking advantage of such features and have them work.  I'm asking the
>>working group to seriously consider whether support for new IPsec
>>requirements should be added to Kink.  The result of this
>>consideration needs to be either modifications to the protocol to add
>>the necessary support or text explaining what features are not
>>supported and why the working group has chosen not to support them.
>>
>>--Sam

--
Kazunori Miyazawa



From owner-ietf-kink@mail.vpnc.org  Wed Jan 19 20:27:51 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16470
	for <kink-archive@lists.ietf.org>; Wed, 19 Jan 2005 20:27:50 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K1MfRx055460;
	Wed, 19 Jan 2005 17:22:42 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0K1MfdM055458;
	Wed, 19 Jan 2005 17:22:41 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from march.taca.jp (vbox.nezu.wide.ad.jp [203.178.142.195])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K1MfG3054647
	for <ietf-kink@vpnc.org>; Wed, 19 Jan 2005 17:22:41 -0800 (PST)
	(envelope-from nov@tahi.org)
Received: from localhost (vbox.nezu.wide.ad.jp [203.178.142.195])
	by march.taca.jp (Postfix) with ESMTP
	id B3FF61FBC4; Thu, 20 Jan 2005 10:22:16 +0900 (JST)
Date: Thu, 20 Jan 2005 10:22:07 +0900 (JST)
Message-Id: <20050120.102207.68299999.nov@tahi.org>
To: hartmans-ietf@mit.edu
Cc: ietf-kink@vpnc.org
Subject: Re: AD review: draft-ietf-kink-kink [section 1-4]
From: Nobuo OKABE <nov@tahi.org>
In-Reply-To: <tslzmz65pzn.fsf@cz.mit.edu>
References: <tslzmz65pzn.fsf@cz.mit.edu>
X-Mailer: Mew version 4.1 on Emacs 20.7 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


From: Sam Hartman <hartmans-ietf@mit.edu>
Subject: AD review: draft-ietf-kink-kink [section 1-4]
Date: Tue, 18 Jan 2005 17:31:08 -0500

> I'd recommend reading draft-ietf-ipsec-rfc2401bis,
> draft-ietf-krb-wg-crypto and skimming
> draft-ietf-krb-wg-kerberos-clarifications.
> 
> Rfc2401bis is setting before the IESG; there are some discusses
> although I expect the document to be approved by IETF 62.
> 
> The Kerberos documents have been approved and are in the RFC editor
> queue.  The crypto document is actually in auth48 waiting for Ken to
> confirm some final edits.

I agree if 2401bis is fixed soon.
However, we can have another way if it is not fixed by IETF62.

    From implementor's viewpoint,
    it seems good to improve/fix the draft based upon 2401,
    then to write another draft based upon 2401bis
    because we need to fix the draft ASAP.

It seems fair to me to postpone the date of fixing the milestones
from February 7 to after IETF62.
Because the progress of 1401bis has impact against the KINK draft.

So I would like to ask chairs to have a meeting in IETF62.

    The deadlines (and/or basic direction like the above)
    seems to need face2face meeting,
    though detail technical discussion can be done on the ML.

    Official meeting might be unnecessary.
    # There might be a low attendance, I guess...

thanks,

----- nobuo



From owner-ietf-kink@mail.vpnc.org  Wed Jan 19 20:29:40 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA16697
	for <kink-archive@lists.ietf.org>; Wed, 19 Jan 2005 20:29:39 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K1Oahv057364;
	Wed, 19 Jan 2005 17:24:36 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0K1OaoB057363;
	Wed, 19 Jan 2005 17:24:36 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from papa.tanu.org (kame195.kame.net [203.178.141.195])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K1OZV0057210
	for <ietf-kink@vpnc.org>; Wed, 19 Jan 2005 17:24:35 -0800 (PST)
	(envelope-from sakane@kame.net)
Received: from localhost (cp.64translator.com [202.214.123.2])
	by papa.tanu.org (8.12.9/8.12.8) with ESMTP id j0K1OUhB025373
	for <ietf-kink@vpnc.org>; Thu, 20 Jan 2005 10:24:30 +0900 (JST)
	(envelope-from sakane@kame.net)
To: ietf-kink@vpnc.org
Subject: who will edit the draft ?
X-Mailer: Cue version 0.8 (041108-2350/sakane)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Message-Id: <20050120102450Q.sakane@kame.net>
Date: Thu, 20 Jan 2005 10:24:50 +0900
From: Shoichi Sakane <sakane@kame.net>
X-Dispatcher: imput version 20030322(IM144)
Lines: 44
X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c
	on papa.tanu.org
X-Virus-Status: Clean
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


WG chairs,

I am also interested in the KINK protocol, and have a experience
to discuss the specification, to implement it in our team.  And I
am developping a IKE daemon in the KAME project.  So I can be reviewer
from the KINK and IPsec point of view.

There are some comments about the draft in the mailing list.
Who will collect these comments and will edit the draft ?
If no one did or will do that, our team is ready to gather them
and will edit the draft.

There are some people interested in the protocol.  I think that we
should have a meeting in order to manage the KINK WG.  I am not sure
that "manage" is suitable word.  To complete the KINK specification may
be suitable.  We have two items at least.  One is to make a consensus
the modification of current draft.  Second is to discuss how to
manage the WG.  I dont mind that the scale of the meeting is
a WG meeting, a BoF, a closed meeting or a lunch meeting.
I want to know who will join the meeting.  Of course I will.

And we have to make a milestone ASAP.  Here is from "Goals and Milestones"
in the WG page,

Done	  	Reach Consensus on requirements document
Done	  	Meet at San Diego IETF to review drafts
Jan 01	  	Reach Consensus on base draft protocol
Feb 01	  	Conduct WG last call on base draft prototol
Mar 01	  	Begin Interoperability bakeoffs
Aug 01	  	Document interoperability results.
                Make decision to recycle or move forward

The items would be:

Feb 14          Submit draft kink-07 with editorial modifications.
Mar 01          Review the issue of current draft, kink-06.
Apr 01          Reach Consensus on draft.
May 01          Resubmit revised draft as Proposed Standard.
Aug 01   	Begin Interoperability bakeoffs.
Sep 01   	Document interoperability results.

If the chair has had the set already, I am sorry for my meddling,
but at least I have not seen yet.  Thease are just my opinion,
any comment welcome.  That would be help for the chairs.



From owner-ietf-kink@mail.vpnc.org  Wed Jan 19 20:40:05 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17664
	for <kink-archive@lists.ietf.org>; Wed, 19 Jan 2005 20:40:04 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K1aDfx073006;
	Wed, 19 Jan 2005 17:36:13 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0K1aDeB073003;
	Wed, 19 Jan 2005 17:36:13 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from nasten.nanohz.org (usen-220x218x5x242.ap-US00.usen.ad.jp [220.218.5.242])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K1aD94072556
	for <ietf-kink@vpnc.org>; Wed, 19 Jan 2005 17:36:13 -0800 (PST)
	(envelope-from kamada@nanohz.org)
Received: from nasten.nanohz.org (localhost [127.0.0.1])
	by nasten.nanohz.org (Postfix) with ESMTP id 6B9D511
	for <ietf-kink@vpnc.org>; Thu, 20 Jan 2005 10:35:49 +0900 (JST)
Received: from mitana.nanohz.org ([2001:240:2:0:202:8aff:fefa:bec0])
	by nasten.nanohz.org (smtpsugar 1.1) with ESMTPA
	id 3d3tx3; Thu, 20 Jan 2005 10:35:49 +0900 (JST)
Date: Thu, 20 Jan 2005 10:36:39 +0900
Message-ID: <20050120103639RZ%kamada@nanohz.org>
From: "KAMADA Ken'ichi" <kamada@nanohz.org>
To: ietf-kink@vpnc.org
Subject: Re: who will edit the draft ?
In-Reply-To: <20050120102450Q.sakane@kame.net>
References: <20050120102450Q.sakane@kame.net>
User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.3.50
 (i386-unknown-netbsdelf2.0G) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=ISO-2022-JP
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


At Thu, 20 Jan 2005 10:24:50 +0900,
Shoichi Sakane <sakane@kame.net> wrote:
> 
> There are some comments about the draft in the mailing list.
> Who will collect these comments and will edit the draft ?

I'm now merging them.  Just a moment please.

-- 
$B3yED7r0l(B <kamada@nanohz.org>



From owner-ietf-kink@mail.vpnc.org  Wed Jan 19 20:51:18 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18673
	for <kink-archive@lists.ietf.org>; Wed, 19 Jan 2005 20:51:18 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K1jBZe086013;
	Wed, 19 Jan 2005 17:45:11 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0K1jBwp086012;
	Wed, 19 Jan 2005 17:45:11 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from dogbert.ihtfp.org (me@DOGBERT.IHTFP.ORG [204.107.200.33])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K1j6kY085721
	for <ietf-kink@vpnc.org>; Wed, 19 Jan 2005 17:45:07 -0800 (PST)
	(envelope-from warlord@MIT.EDU)
Received: (from warlord@localhost) by dogbert.ihtfp.org (8.12.9)
	id j0K1j2TK006492; Wed, 19 Jan 2005 20:45:02 -0500
To: Shoichi Sakane <sakane@kame.net>
Cc: ietf-kink@vpnc.org
Subject: Re: who will edit the draft ?
References: <20050120102450Q.sakane@kame.net>
From: Derek Atkins <derek@ihtfp.com>
Date: Wed, 19 Jan 2005 20:45:02 -0500
In-Reply-To: <20050120102450Q.sakane@kame.net> (Shoichi Sakane's message of
 "Thu, 20 Jan 2005 10:24:50 +0900")
Message-ID: <sjmis5syiu9.fsf@dogbert.ihtfp.org>
User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


Hi,

Shoichi Sakane <sakane@kame.net> writes:

> WG chairs,
>
> I am also interested in the KINK protocol, and have a experience
> to discuss the specification, to implement it in our team.  And I
> am developping a IKE daemon in the KAME project.  So I can be reviewer
> from the KINK and IPsec point of view.

Good to know.  Thank you for volunteering.  At this time Mike Thomas
has agreed to continue to edit the draft, so unless he becomes
unresponsive I see no reason immediately to appoint a new draft
editor.

[snip]
> And we have to make a milestone ASAP.  Here is from "Goals and Milestones"
> in the WG page,
>
> Done	  	Reach Consensus on requirements document
> Done	  	Meet at San Diego IETF to review drafts
> Jan 01	  	Reach Consensus on base draft protocol
> Feb 01	  	Conduct WG last call on base draft prototol
> Mar 01	  	Begin Interoperability bakeoffs
> Aug 01	  	Document interoperability results.
>                 Make decision to recycle or move forward
>
> The items would be:
>
> Feb 14          Submit draft kink-07 with editorial modifications.
> Mar 01          Review the issue of current draft, kink-06.
> Apr 01          Reach Consensus on draft.
> May 01          Resubmit revised draft as Proposed Standard.
> Aug 01   	Begin Interoperability bakeoffs.
> Sep 01   	Document interoperability results.
>
> If the chair has had the set already, I am sorry for my meddling,
> but at least I have not seen yet.  Thease are just my opinion,
> any comment welcome.  That would be help for the chairs.

The dates are Month / Year, not Month / Day.  So I think you
probably mean Feb 05, Mar 05, ...

Based on the existing set of issues I do not believe that your
suggestions are reasonable -- they are way too aggresive.  I really do
not believe that we'll reach consensus by April.  I think we have way
too many issues.  Perhaps a better proposal for milestones are:

Mar 05	Review issues with kink-06
Mar 05	Submit kink-07
Jun 05	Reach consensus on necessary changes
Jul 05	Submit kink-08
Aug 05	WGLC
Sep 05	Submit draft to IESG
Jan 06	Begin Interop bakeoffs
Feb 06	Document interop results.

Even this schedule is extremely agrressive, but IMHO actually
achievable.  I don't think we can get concensus on all the open issues
and make it past the IESG before Paris.

-derek

-- 
       Derek Atkins                 617-623-3745
       derek@ihtfp.com             www.ihtfp.com
       Computer and Internet Security Consultant



From owner-ietf-kink@mail.vpnc.org  Wed Jan 19 20:55:19 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19197
	for <kink-archive@lists.ietf.org>; Wed, 19 Jan 2005 20:55:18 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K1pwcD095155;
	Wed, 19 Jan 2005 17:51:58 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0K1pwTV095153;
	Wed, 19 Jan 2005 17:51:58 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K1pvBn094993
	for <ietf-kink@vpnc.org>; Wed, 19 Jan 2005 17:51:57 -0800 (PST)
	(envelope-from mat@cisco.com)
Received: from sj-core-4.cisco.com (171.68.223.138)
  by sj-iport-4.cisco.com with ESMTP; 19 Jan 2005 17:53:06 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id j0K1pl1M021733;
	Wed, 19 Jan 2005 17:51:47 -0800 (PST)
Received: from thomasm-lnx.cisco.com (thomasm-lnx.cisco.com [171.71.96.50])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j0K1mJY5028176;
	Wed, 19 Jan 2005 17:48:19 -0800
Subject: Re: who will edit the draft ?
From: Michael Thomas <mat@cisco.com>
To: Shoichi Sakane <sakane@kame.net>
Cc: ietf-kink@vpnc.org
In-Reply-To: <20050120102450Q.sakane@kame.net>
References: <20050120102450Q.sakane@kame.net>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-dOpC4YXrVShRLI2Y5hnB"
Organization: Cisco Systems
Message-Id: <1106185907.2953.37.camel@thomasm-lnx.cisco.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 
Date: Wed, 19 Jan 2005 17:51:47 -0800
IIM-SIG: v:"1.1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1106185699.249935"; x:"432200"; a:"rsa-sha1"; b:"nofws:2406";
	e:"Iw=="; n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2p"
	"XIweAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRUtW+c43sl9jC"
	"50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"lYTYgOfFtmtYJBM+b9khUKjDQrVfSedAklDoszW2XbXc0OM4QTgOg8rb0RVEHK3gkzQ9utKX"
	"gq9bEkiC71XiKlOEZWl0AWhshk2a+TwiSM/AtY5i75ggerlvkmgcOVZ3uTJ/GDwL6j+PyfPpyvd"
	"UgHIMu8WiQEuPWnf9Fu/SvQc=";
	c:"Subject: Re: who will edit the draft ?";
	c:"From: Michael Thomas <mat@cisco.com>";
	c:"Date: Wed, 19 Jan 2005 17:51:47 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>



--=-dOpC4YXrVShRLI2Y5hnB
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

I'm still willing to edit the draft if we're not
talking about wholesale changes, and we're talking
about a relatively modest amount of time (eg, a=20
few months).=20

Has a decision been made on wg meeting in MPLS?
I'm hoping that the issues don't require a f2f=20
meeting, but it would be good to know one way or
the other.

		Mike

On Wed, 2005-01-19 at 17:24, Shoichi Sakane wrote:
> WG chairs,
>=20
> I am also interested in the KINK protocol, and have a experience
> to discuss the specification, to implement it in our team.  And I
> am developping a IKE daemon in the KAME project.  So I can be reviewer
> from the KINK and IPsec point of view.
>=20
> There are some comments about the draft in the mailing list.
> Who will collect these comments and will edit the draft ?
> If no one did or will do that, our team is ready to gather them
> and will edit the draft.
>=20
> There are some people interested in the protocol.  I think that we
> should have a meeting in order to manage the KINK WG.  I am not sure
> that "manage" is suitable word.  To complete the KINK specification may
> be suitable.  We have two items at least.  One is to make a consensus
> the modification of current draft.  Second is to discuss how to
> manage the WG.  I dont mind that the scale of the meeting is
> a WG meeting, a BoF, a closed meeting or a lunch meeting.
> I want to know who will join the meeting.  Of course I will.
>=20
> And we have to make a milestone ASAP.  Here is from "Goals and Milestones=
"
> in the WG page,
>=20
> Done	  	Reach Consensus on requirements document
> Done	  	Meet at San Diego IETF to review drafts
> Jan 01	  	Reach Consensus on base draft protocol
> Feb 01	  	Conduct WG last call on base draft prototol
> Mar 01	  	Begin Interoperability bakeoffs
> Aug 01	  	Document interoperability results.
>                 Make decision to recycle or move forward
>=20
> The items would be:
>=20
> Feb 14          Submit draft kink-07 with editorial modifications.
> Mar 01          Review the issue of current draft, kink-06.
> Apr 01          Reach Consensus on draft.
> May 01          Resubmit revised draft as Proposed Standard.
> Aug 01   	Begin Interoperability bakeoffs.
> Sep 01   	Document interoperability results.
>=20
> If the chair has had the set already, I am sorry for my meddling,
> but at least I have not seen yet.  Thease are just my opinion,
> any comment welcome.  That would be help for the chairs.

--=-dOpC4YXrVShRLI2Y5hnB
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iQCVAwUAQe8Os7MsDAj/Eq++AQL92AQAj0kkXCrIouO33S6+3BfbN6bSu+3MmrJN
dMRqgp+aIleFfI9GZFnwyhycgSAixDtBlrM5gl48NvXU3SGOfNlmy3D3iyMXsDIL
eIeiJHG//xuwmWTDEp60l2hvrOvqyUl47QtvAAMHDeLeZp8DhTHwfB4KyP+6ot4E
CfSqcGGTwMg=
=dKxZ
-----END PGP SIGNATURE-----

--=-dOpC4YXrVShRLI2Y5hnB--



From owner-ietf-kink@mail.vpnc.org  Wed Jan 19 21:06:14 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19962
	for <kink-archive@lists.ietf.org>; Wed, 19 Jan 2005 21:06:14 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K23DbS010940;
	Wed, 19 Jan 2005 18:03:13 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0K23DrX010939;
	Wed, 19 Jan 2005 18:03:13 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from dogbert.ihtfp.org (me@DOGBERT.IHTFP.ORG [204.107.200.33])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K23Cpx010915
	for <ietf-kink@vpnc.org>; Wed, 19 Jan 2005 18:03:13 -0800 (PST)
	(envelope-from warlord@MIT.EDU)
Received: (from warlord@localhost) by dogbert.ihtfp.org (8.12.9)
	id j0K239R0006567; Wed, 19 Jan 2005 21:03:09 -0500
To: Michael Thomas <mat@cisco.com>
Cc: Shoichi Sakane <sakane@kame.net>, ietf-kink@vpnc.org
Subject: Re: who will edit the draft ?
References: <20050120102450Q.sakane@kame.net>
	<1106185907.2953.37.camel@thomasm-lnx.cisco.com>
From: Derek Atkins <derek@ihtfp.com>
Date: Wed, 19 Jan 2005 21:03:09 -0500
In-Reply-To: <1106185907.2953.37.camel@thomasm-lnx.cisco.com> (Michael
 Thomas's message of "Wed, 19 Jan 2005 17:51:47 -0800")
Message-ID: <sjm651syi02.fsf@dogbert.ihtfp.org>
User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


Hi,

Michael Thomas <mat@cisco.com> writes:

> I'm still willing to edit the draft if we're not
> talking about wholesale changes, and we're talking
> about a relatively modest amount of time (eg, a 
> few months). 

I hope it'll only take a few months, but I know Sam is going to be a
stickler for quality before the IESG.  This isn't a bad thing, but I
think it's going to put a lot more scrutiny on the document, so it may
be significantly more work than you expect at the moment.  It's hard
to say right now.

At the face of it we need to update the document to meet the new
format requirements, update to krb-clarifications and krb-crypto, and
probably update to reference IKEv2 and 2401bis.  I dont know what
other changes are going to be required.

So, if you're willing (and able) to put in the time and effort to
remain the editor I'm happy to keep you.  However if you feel that you
cannot commit to the task I'd ask that we find someone else.  I leave
that choice up to you for now.

> Has a decision been made on wg meeting in MPLS?
> I'm hoping that the issues don't require a f2f 
> meeting, but it would be good to know one way or
> the other.

I'm willing to go either way.  If the WG believes we need a face to
face meeting then I'll gladly arrange for one.

> 		Mike

-derek

-- 
       Derek Atkins                 617-623-3745
       derek@ihtfp.com             www.ihtfp.com
       Computer and Internet Security Consultant



From owner-ietf-kink@mail.vpnc.org  Wed Jan 19 21:07:30 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20052
	for <kink-archive@lists.ietf.org>; Wed, 19 Jan 2005 21:07:29 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K240At011590;
	Wed, 19 Jan 2005 18:04:00 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0K240AO011589;
	Wed, 19 Jan 2005 18:04:00 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from nasten.nanohz.org (usen-220x218x5x242.ap-US00.usen.ad.jp [220.218.5.242])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K23xEi011579
	for <ietf-kink@vpnc.org>; Wed, 19 Jan 2005 18:03:59 -0800 (PST)
	(envelope-from kamada@nanohz.org)
Received: from nasten.nanohz.org (localhost [127.0.0.1])
	by nasten.nanohz.org (Postfix) with ESMTP id 952C911
	for <ietf-kink@vpnc.org>; Thu, 20 Jan 2005 11:03:58 +0900 (JST)
Received: from mitana.nanohz.org ([2001:240:2:0:202:8aff:fefa:bec0])
	by nasten.nanohz.org (smtpsugar 1.1) with ESMTPA
	id 24Um0S; Thu, 20 Jan 2005 11:03:58 +0900 (JST)
Date: Thu, 20 Jan 2005 11:04:48 +0900
Message-ID: <20050120110448RR%kamada@nanohz.org>
From: "KAMADA Ken'ichi" <kamada@nanohz.org>
To: ietf-kink@vpnc.org
Subject: KINK issue list
In-Reply-To: <20050120103639RZ%kamada@nanohz.org>
References: <20050120102450Q.sakane@kame.net>
	<20050120103639RZ%kamada@nanohz.org>
User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.3.50
 (i386-unknown-netbsdelf2.0G) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


Here is a merged version of KINK issues expressed till now.
If I missed some of them you noted, please let me know.


[**] Indicates an issue considered substantive.
[-] Indicates an editorial issue.


[**] user-to-user (section 3 and 4.2)

	It seems like the
	server tells the client what principal to authenticate to, but this
	principal is not properly authorized.  (Sam Hartman)

	More examination of user-to-user case, especially situations where 
	it might *not* be two PKINIT clients, which section 3 says is possible. 
	(BTW, in the Kerberos docs, it's "user-to-user", not "user-user".)
	(Ken Raeburn)

	Verifying remotely supplied identity, as Sam raised earlier.
	(Ken Raeburn)

	In the user-to-user case with TGTs, I think the KINK draft may be 
	over-specifying things that should be dealt with at the Kerberos level. 
	If things are underspecified in Kerberos Clarifications, let's deal 
	with that.  (Ken Raeburn)

	Section 4.2:
	[**] How will the initiator determine whether it will be able to get a
	TGT?  I think policy considerations of when to use u2u and
	authorization considerations of what u2u principals are authorized are
	underspecified in the draft.
	(Sam Hartman)

	[**] Make sure the descriptions of u2u work correctly in the
	cross-realm case.
	(Sam Hartman)


[**] CREATE Security Association from the aspect of 2401bis (section 4.3)

	[**] I need explicit review from the IPsec reviewer of this section to
	make sure it is compatible with 2401bis.  IN addition, any differences
	between how this works and how IKE would set up the same SA need to be
	called out.  It is fine for there to be differences, but I want to
	make sure the working group explicitly decided the differences are a
	good thing.

	I'm somewhat concerned that 4.3 is not specific enough to describe
	exactly what key gets set up.  I.E. I'm concerned it may not be
	detailed enough for interoperable implementations.
	(Sam Hartman)


[*] When 3-way, is responder's nonce MUST or SHOULD? (section 4.3 and 7.3)

	Sec 4.3 and 7.3 use SHOULD and MUST respectively regarding when the 
	nonce should be used.  If the circumstances they're describing are 
	different, that's okay, but if so, I missed it on first reading.
	(Ken Raeburn)


[*] Half open (section 4.4)

	IPsec does not allow half-open security associations any more as far
	as I can tell in 2401bis.  So it's not just for simplicity, but for
	model conformance.  (Sam Hartman)


[**] Section 4.4.2

	[**] Discuss status message, rebooting peers and u2u.  This looks a
	lot like the IKE case where you lose all cryptographic context to me.


[*] CksumLen (section 5)

	Diagram indicates one octet for cksumlen, but the text (and 
	kcrypto specifications) say it should be two.


[**] etype does not directly indicate checksum type (section 5)

	a key's encryption type does not directly indicate 
	a checksum type, it indicates an encryption(-with-integrity-protection) 
	scheme, which does include a required-to-implement checksum type
	(Ken Raeburn)


[**] Kerberos allows variable length checksum (section 5)

	I'd have to go back and check, but I don't think we require that 
	a given checksum type have a fixed output size, so "leave X amount of 
	space and fill it with zero for computing the checksum" is questionable 
	too.  (Ken Raeburn)


[*] Kerberos checksum is not deterministic (section 5)

	The Kink description of how to verify a checksum assumes that
	Kerberos checksums are deterministic; this is not strictly required.
	(Sam Hartman)

	let kcrypto specify how 
	to verify a checksum, as they're not required to be deterministic, so 
	the "compute it again and compare" approach specified in section 5 is 
	wrong  (Ken Raeburn)

	The spec should describe how to verify checksum as follows.

	To verify the checksum, the checksum is saved, and the
	checksum field is zeroed out.  The resulting message and the saved
	checksum are passed to the verification function.  If the verification
	fails, the message MUST be dropped.


[*] Subsession keys (section 5 and 8)

	Are subsession keys ignored?  (Ken Raeburn)


[**] Checksum when KRB-ERROR occured (section 5.1.4 and 7.1)

	Section 7.1 says the checksum in the KRB-ERROR message is not used,
	but section 5.1.4 says that KINK implementation MUST make use of
	keyed Kerberos errors.  But KRB-ERROR does not have checksum in it (at
	least with RFC 1510 or kerberos-clarifications).
	I think a correct phrase here is "KINK implementations MUST make use of
	a KINK Cksum field when returning KINK_KRB_ERROR and the appropriate
	service key is available."


[**] KINK_ENCRYPT format (section 5.1.8)

	The format of the encrypted part of KINK_ENCRYPT (section 5.1.8) is
	vague.  I think of using the output of raw encryption algorithms
	(i.e. E(confounder | plaintext | pad)) or using EncryptedData.

	treat "encryption with 
	integrity protection" output as a whole, don't peek under the covers to 
	find a "checksum" part you can throw away  (Ken Raeburn)

	drop references to the initialization vector  (Ken Raeburn)


[*] Kerberos PFS (section 6.8)

	Sec 6.8: "Kerberos in general does not provide FPS so it is somewhat 
	questionable whether a system which is heavily relying on Kerberos 
	benefits from PFS."  First, that sounds like it might be Security 
	Considerations material.  Second, I don't follow; explain please?
	(Ken Raeburn)


[*] MUST/SHOULD in clock skew (section 7.1)

	The time difference MUST be computed and SHOULD be stored 
	and used?  Why the different requirement levels?  (And is this sort of 
	thing in the domain of KINK or Kerberos?)  (Ken Raeburn)


[**] prf (section 8)

	Section 8 says "prf is the same hash algorithm found in the session
	ticket's etype", but krb-wg-crypto-07 defines hash as unkeyed.
	Fortunately krb-wg-crypto-07 defines a PRF for each etype, so KINK
	should use this PRF.

	Use a prf 
	from kcrypto, don't assume the checksum operations are deterministic 
	hash functions  (Ken Raeburn)



[*] Key derivation (section 8)

	The key derivation seems inconsistent with the crypto framework
	document.  (Sam Hartman)


[*] Key usage

	Usage of  kink should specify the key usage numbers for kerberos
	encryption.  (Sam Hartman)


[*] 2401bis

	section 4.4.1:
	Please make sure this discussion is aligned with 2401bis.  I think it
	may change small details but they seem to have adopted much of the
	same strategy kink uses.  The area wher I believe they speak to this
	issue is when you should rekey (timers etc)


[*] IKEv2

	Should we adopt IKEv2?

	If we should...
	- IKEv2 does not have DOI, so how to handle the DOI field in the KINK
	  packet header should be described.
	- Use TS (Traffic Selector) instead of ID (Identification).
	- KEYMAT calculation is changed.
	- How to handle REKEY_SA Notify type.


[*] behavior on KINK_ERROR

	In implementor's point of view, I'd like to see initiator's
	behavior in receiving KINK_ERROR to be defined.
	For example:
	- When KINK_OK is received, initiator MAY act as if the KINK_ERROR
	  payload was not included in the messaged.
	- When KINK_BADQMVERS is received and the Cksum is verified,
	  initiator MAY retry in other Quick Mode version.
	- When one of other error codes is received and the Cksum is verified,
	  initiator SHOULD abort the negotiation.


[-] I-D nits

	Review the I-D nits and RFC authors docs.  I spotted a lot of 
	mechanical things (number of lines per page; avoid hyphenation; use 
	ragged right margin; need two spaces after sentence-ending period; fix 
	page numbers in table of contents; add section numbers to TOC) most of 
	which I think are specified in one of those documents.
	(Ken Raeburn)

	the document needs to meet all the ID nits when it is
	submitted.  (Sam Hartman)


[-] IANA considerations

	I think the correct terminology is "port 
	number", not "port", and they're "assigned", not "created".  This 
	section says no new registries are required in the first paragraph, and 
	the third one specifies that IANA must create one (but without the 
	associated procedural data that is required nowadays).  Are the KINK 
	payload types and ISAKMP payload types actually ever used in the same 
	field?  If not, I don't think they need to come out of the same 
	registry.  (Ken Raeburn)


[-] Wording/Terminology

	Section 2 and 10.1.
	Kerberos is now using the term user-user rather than user-to-user.
	(Sam Hartman)

	Section 2.
	Principals are not either client or service principals;
	they can and often do fill both roles.  (Sam Hartman)

	Section 2, last paragraph.  "Between" is generally non-directional, 
	but in this case, a direction seems to be intended to be inferred; try 
	"from...to" instead.  (Ken Raeburn)

	Section 3, English usage/grammar problems with the first two paragraphs.
	(Sam Hartman)

	Section 3.
	   which allows a final acknowledgment message when the respondent needs
	   a full three-way handshake. This is only needed when the optimistic
	   keying route is not taken, though it is expected that that will not
	   be the norm. KINK also provides rekeying and dead peer detection as
	What is expected not to be the norm?  Please reword.
	(Sam Hartman)

	Section 4.3, discussing attributes, mixes singular and plural 
	indications.  The word "lone" appears to be popular with the author, 
	too. :-)  (Ken Raeburn)

	Sec 8: "By optional, it is meant..." is badly worded.  (Ken Raeburn)


[-] References

	The reference to [PKCROSS] is unnecessary, and only happens once, in 
	the introduction.  I'd suggest dropping it.  That's one less 
	unpublished I-D in the references section.  (Ken Raeburn)

	[KRBREVS] is referenced but not listed in the references section.
	(Ken Raeburn)

	Sec 5.1.7, next to last paragraph on page 21, is "IKE" (the 
	protocol) fuzzy about use of different SAs, or is it "[IKE]" (the 
	document)?  (Ken Raeburn)

	Section 1:
	Remove the reference to pkcross or cite something outside the IETF.
	It's an expired ID without and active editor.  (Sam Hartman)

	Section 1:
	Add an informative reference to IKE.  (Sam Hartman)

	Section 2:
	Cite a reference for DER.  (Sam Hartman)


[-] Typos

	4.4.2. Dead Peer Detection
	In the fourth paragraph, "loose" is to be "lose".

	5.1.1. KINK Padding Rules
	In the second item, "other other" is to be "other".

	5.1.1. KINK Padding Rules
	The first item in the list should end with a period like 
	the others.  (Ken Raeburn)

	5.1.5. KINK_TGT_REQ Payload
	In the third item, "krbtgt/REALM/@REALM" is to be "krbtgt/REALM@REALM".

	5.1.6. KINK_TGT_REP Payload
	In the caption of Figure 13, "KINK_TGT_REQ" is to be "KINK_TGT_REP".

	7.3. CREATE
	"IPspec" is to be "IPsec".

	7.5. STATUS
	In the last paragraph, "REPLY KINK Header" should be in one line.
	In the last paragraph, "[KRB_ERROR]" is to be "[KINK_ERROR]".

	overall:
	"'s" is used in some places where I'd use "s" for a plural form.


-- 
KAMADA Ken'ichi <kamada@nanohz.org>



From owner-ietf-kink@mail.vpnc.org  Wed Jan 19 21:19:13 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20828
	for <kink-archive@lists.ietf.org>; Wed, 19 Jan 2005 21:19:12 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K2FNbP028083;
	Wed, 19 Jan 2005 18:15:23 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0K2FMKM028079;
	Wed, 19 Jan 2005 18:15:22 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from papa.tanu.org (kame195.kame.net [203.178.141.195])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K2FK4N028007
	for <ietf-kink@vpnc.org>; Wed, 19 Jan 2005 18:15:20 -0800 (PST)
	(envelope-from sakane@kame.net)
Received: from localhost (cp.64translator.com [202.214.123.2])
	by papa.tanu.org (8.12.9/8.12.8) with ESMTP id j0K2FThB025737
	for <ietf-kink@vpnc.org>; Thu, 20 Jan 2005 11:15:29 +0900 (JST)
	(envelope-from sakane@kame.net)
To: ietf-kink@vpnc.org
Subject: KINK should referenece to IKEv2?
X-Mailer: Cue version 0.8 (041108-2350/sakane)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Message-Id: <20050120111553S.sakane@kame.net>
Date: Thu, 20 Jan 2005 11:15:53 +0900
From: Shoichi Sakane <sakane@kame.net>
X-Dispatcher: imput version 20030322(IM144)
Lines: 4
X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c
	on papa.tanu.org
X-Virus-Status: Clean
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


In my opinion from reading the minutes at the IETF50 minneapolis,
there is no strict reason to change the referenece from IKEv1 to IKEv2
because the ISAKMP payload in the KINK is just used to carry a set of
IPsec parameters, and Notification Payloads.



From owner-ietf-kink@mail.vpnc.org  Wed Jan 19 21:36:36 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22189
	for <kink-archive@lists.ietf.org>; Wed, 19 Jan 2005 21:36:36 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K2Vl5j050227;
	Wed, 19 Jan 2005 18:31:47 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0K2VlZq050226;
	Wed, 19 Jan 2005 18:31:47 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from miyazawa.org (usen-221x116x13x66.ap-US01.usen.ad.jp [221.116.13.66])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K2VktE049685
	for <ietf-kink@vpnc.org>; Wed, 19 Jan 2005 18:31:47 -0800 (PST)
	(envelope-from kazunori@miyazawa.org)
Received: from [IPv6:2001:240:2:0:c926:991b:c386:a4d7] ([2001:240:2:0:c926:991b:c386:a4d7])
  (AUTH: LOGIN kazunori, SSL: TLSv1/SSLv3,128bits,RC4-MD5)
  by miyazawa.org with esmtp; Thu, 20 Jan 2005 11:25:08 +0900
  id 000008FF.41EF1684.00007195
Message-ID: <41EF17D7.4060108@miyazawa.org>
Date: Thu, 20 Jan 2005 11:30:47 +0900
From: Kazunori Miyazawa <kazunori@miyazawa.org>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Shoichi Sakane <sakane@kame.net>
CC: ietf-kink@vpnc.org
Subject: Re: KINK should referenece to IKEv2?
References: <20050120111553S.sakane@kame.net>
In-Reply-To: <20050120111553S.sakane@kame.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


Shoichi Sakane wrote:
> In my opinion from reading the minutes at the IETF50 minneapolis,
> there is no strict reason to change the referenece from IKEv1 to IKEv2
> because the ISAKMP payload in the KINK is just used to carry a set of
> IPsec parameters, and Notification Payloads.
> 

We should have a consensus whether we will discuss KINK based on rfc2401bis
or rfc2401.

--
Kazunori Miyazawa



From owner-ietf-kink@mail.vpnc.org  Wed Jan 19 22:28:30 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25919
	for <kink-archive@lists.ietf.org>; Wed, 19 Jan 2005 22:28:29 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K3JoYr006554;
	Wed, 19 Jan 2005 19:19:50 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0K3Jogh006553;
	Wed, 19 Jan 2005 19:19:50 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from papa.tanu.org (kame195.kame.net [203.178.141.195])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K3JiUp006491
	for <ietf-kink@vpnc.org>; Wed, 19 Jan 2005 19:19:49 -0800 (PST)
	(envelope-from sakane@kame.net)
Received: from localhost (cp.64translator.com [202.214.123.2])
	by papa.tanu.org (8.12.9/8.12.8) with ESMTP id j0K3JrhB026129
	for <ietf-kink@vpnc.org>; Thu, 20 Jan 2005 12:19:54 +0900 (JST)
	(envelope-from sakane@kame.net)
To: ietf-kink@vpnc.org
Subject: Re: KINK should referenece to IKEv2?
In-Reply-To: Your message of "Thu, 20 Jan 2005 11:30:47 +0900"
	<41EF17D7.4060108@miyazawa.org>
References: <41EF17D7.4060108@miyazawa.org>
X-Mailer: Cue version 0.8 (041108-2350/sakane)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Message-Id: <20050120122017V.sakane@kame.net>
Date: Thu, 20 Jan 2005 12:20:17 +0900
From: Shoichi Sakane <sakane@kame.net>
X-Dispatcher: imput version 20030322(IM144)
Lines: 23
X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c
	on papa.tanu.org
X-Virus-Status: Clean
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


> > In my opinion from reading the minutes at the IETF50 minneapolis,
> > there is no strict reason to change the referenece from IKEv1 to IKEv2
> > because the ISAKMP payload in the KINK is just used to carry a set of
> > IPsec parameters, and Notification Payloads.

> We should have a consensus whether we will discuss KINK based on rfc2401bis
> or rfc2401.

Well I put on a KINK hat, if the KINK specification will conform to
rfc2401bis and if the KINK won't work on the stack based on *RFC2401*,
we won't be happy because it will take long time to deploy the stack
based on rfc2401bis.  so we need to implement a stack based on rfc2401bis
first before we will run a KINK function.

so we can have four choices while researching the difference between
2401bis and RFC2401 from KINK requirement of view:

	1. make a standard base on both rfc2401 and IKEv1.
	2. make a standard base on both rfc2401 and IKEv2.
	3. make a standard base on both 2401bis and IKEv1.
	4. make a standard base on both 2401bis and IKEv2.

I would like #1 then we proceed to #4.



From owner-ietf-kink@mail.vpnc.org  Wed Jan 19 23:00:25 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00475
	for <kink-archive@lists.ietf.org>; Wed, 19 Jan 2005 23:00:23 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K3urII056066;
	Wed, 19 Jan 2005 19:56:53 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0K3urDO056065;
	Wed, 19 Jan 2005 19:56:53 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from march.taca.jp (vbox.nezu.wide.ad.jp [203.178.142.195])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K3uhxu056031
	for <ietf-kink@vpnc.org>; Wed, 19 Jan 2005 19:56:48 -0800 (PST)
	(envelope-from nov@tahi.org)
Received: from localhost (vbox.nezu.wide.ad.jp [203.178.142.195])
	by march.taca.jp (Postfix) with ESMTP
	id CBBAE1FBC2; Thu, 20 Jan 2005 12:56:40 +0900 (JST)
Date: Thu, 20 Jan 2005 12:56:18 +0900 (JST)
Message-Id: <20050120.125618.134143696.nov@tahi.org>
To: sakane@kame.net
Cc: ietf-kink@vpnc.org
Subject: Re: KINK should referenece to IKEv2?
From: Nobuo OKABE <nov@tahi.org>
In-Reply-To: <20050120122017V.sakane@kame.net>
References: <41EF17D7.4060108@miyazawa.org>
	<20050120122017V.sakane@kame.net>
X-Mailer: Mew version 4.1 on Emacs 20.7 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


From: Shoichi Sakane <sakane@kame.net>
Subject: Re: KINK should referenece to IKEv2?
Date: Thu, 20 Jan 2005 12:20:17 +0900

> so we can have four choices while researching the difference between
> 2401bis and RFC2401 from KINK requirement of view:
> 
> 	1. make a standard base on both rfc2401 and IKEv1.
> 	2. make a standard base on both rfc2401 and IKEv2.
> 	3. make a standard base on both 2401bis and IKEv1.
> 	4. make a standard base on both 2401bis and IKEv2.
> 
> I would like #1 then we proceed to #4.

I agree with your choise (i.e. #4) if we can keep new milestones
which the chairs proposed today.

My point is how stable 2401bis is.

----- nobuo



From owner-ietf-kink@mail.vpnc.org  Wed Jan 19 23:07:31 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01025
	for <kink-archive@lists.ietf.org>; Wed, 19 Jan 2005 23:07:30 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K43EtD062050;
	Wed, 19 Jan 2005 20:03:14 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0K43ESX062049;
	Wed, 19 Jan 2005 20:03:14 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from march.taca.jp (vbox.nezu.wide.ad.jp [203.178.142.195])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K43DMv062026
	for <ietf-kink@vpnc.org>; Wed, 19 Jan 2005 20:03:13 -0800 (PST)
	(envelope-from nov@tahi.org)
Received: from localhost (vbox.nezu.wide.ad.jp [203.178.142.195])
	by march.taca.jp (Postfix) with ESMTP
	id C01C01FBC2; Thu, 20 Jan 2005 13:03:10 +0900 (JST)
Date: Thu, 20 Jan 2005 13:02:59 +0900 (JST)
Message-Id: <20050120.130259.111386852.nov@tahi.org>
To: sakane@kame.net
Cc: ietf-kink@vpnc.org
Subject: Re: KINK should referenece to IKEv2?
From: Nobuo OKABE <nov@tahi.org>
In-Reply-To: <20050120.125618.134143696.nov@tahi.org>
References: <41EF17D7.4060108@miyazawa.org>
	<20050120122017V.sakane@kame.net>
	<20050120.125618.134143696.nov@tahi.org>
X-Mailer: Mew version 4.1 on Emacs 20.7 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


Sorry, I goofed.
Please ignore my previous mail.

I fully agree with sakane-san (i.e. first #1, then #4).

From: Nobuo OKABE <nov@tahi.org>
Subject: Re: KINK should referenece to IKEv2?
Date: Thu, 20 Jan 2005 12:56:18 +0900 (JST)

> From: Shoichi Sakane <sakane@kame.net>
> Subject: Re: KINK should referenece to IKEv2?
> Date: Thu, 20 Jan 2005 12:20:17 +0900
> 
> > so we can have four choices while researching the difference between
> > 2401bis and RFC2401 from KINK requirement of view:
> > 
> > 	1. make a standard base on both rfc2401 and IKEv1.
> > 	2. make a standard base on both rfc2401 and IKEv2.
> > 	3. make a standard base on both 2401bis and IKEv1.
> > 	4. make a standard base on both 2401bis and IKEv2.
> > 
> > I would like #1 then we proceed to #4.
> 
> I agree with your choise (i.e. #4) if we can keep new milestones
> which the chairs proposed today.
> 
> My point is how stable 2401bis is.

----- nobuo



From owner-ietf-kink@mail.vpnc.org  Wed Jan 19 23:16:00 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01661
	for <kink-archive@lists.ietf.org>; Wed, 19 Jan 2005 23:15:59 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K4BOEJ072609;
	Wed, 19 Jan 2005 20:11:24 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0K4BO98072608;
	Wed, 19 Jan 2005 20:11:24 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from biscayne-one-station.mit.edu (BISCAYNE-ONE-STATION.MIT.EDU [18.7.7.80])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K4BKNH072477
	for <ietf-kink@vpnc.org>; Wed, 19 Jan 2005 20:11:20 -0800 (PST)
	(envelope-from raeburn@MIT.EDU)
Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103])
	by biscayne-one-station.mit.edu (8.12.4/8.9.2) with ESMTP id j0K4BHva009347
	for <ietf-kink@vpnc.org>; Wed, 19 Jan 2005 23:11:18 -0500 (EST)
Received: from [18.101.0.226] ([18.101.0.226])
	(authenticated bits=0)
        (User authenticated as raeburn@ATHENA.MIT.EDU)
	by outgoing.mit.edu (8.12.4/8.12.4) with ESMTP id j0K4BE1x007528
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT)
	for <ietf-kink@vpnc.org>; Wed, 19 Jan 2005 23:11:16 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <tslzmz65pzn.fsf@cz.mit.edu>
References: <tslzmz65pzn.fsf@cz.mit.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <500B80B3-6A99-11D9-9F67-000A95909EE2@mit.edu>
Content-Transfer-Encoding: 7bit
From: Ken Raeburn <raeburn@MIT.EDU>
Subject: Re: AD review: draft-ietf-kink-kink [section 1-4]
Date: Wed, 19 Jan 2005 23:11:08 -0500
To: ietf-kink@vpnc.org
X-Mailer: Apple Mail (2.619)
X-Spam-Score: -4.9
X-Spam-Flag: NO
X-Scanned-By: MIMEDefang 2.42
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


On Jan 18, 2005, at 17:31, Sam Hartman wrote:
> Kerberos is now using the term user-user rather than user-to-user.

You've got this backwards, Sam.  Both RFC 1510 and 
draft-ietf-krb-wg-kerberos-clarifications use "user-to-user".

Ken



From owner-ietf-kink@mail.vpnc.org  Wed Jan 19 23:27:55 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA02323
	for <kink-archive@lists.ietf.org>; Wed, 19 Jan 2005 23:27:54 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K4NmVR087608;
	Wed, 19 Jan 2005 20:23:48 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0K4NmDp087607;
	Wed, 19 Jan 2005 20:23:48 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0K4Nj5N087551
	for <ietf-kink@vpnc.org>; Wed, 19 Jan 2005 20:23:47 -0800 (PST)
	(envelope-from vilhuber@cisco.com)
Received: from sj-core-4.cisco.com (171.68.223.138)
  by sj-iport-5.cisco.com with ESMTP; 19 Jan 2005 20:24:57 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from localhost (vilhuber-u30.cisco.com [128.107.162.107])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id j0K4Nb1N012568;
	Wed, 19 Jan 2005 20:23:38 -0800 (PST)
Date: Wed, 19 Jan 2005 20:23:34 -0800 (PST)
From: Jan Vilhuber <vilhuber@cisco.com>
X-X-Sender: vilhuber@mediapc.goinhome.com
To: Derek Atkins <derek@ihtfp.com>
cc: Michael Thomas <mat@cisco.com>, Shoichi Sakane <sakane@kame.net>,
        ietf-kink@vpnc.org
Subject: Re: who will edit the draft ?
In-Reply-To: <sjm651syi02.fsf@dogbert.ihtfp.org>
Message-ID: <Pine.LNX.4.61.0501192022390.8184@mediapc.goinhome.com>
References: <20050120102450Q.sakane@kame.net> <1106185907.2953.37.camel@thomasm-lnx.cisco.com>
 <sjm651syi02.fsf@dogbert.ihtfp.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


On Wed, 19 Jan 2005, Derek Atkins wrote:

> 
> Hi,
> 
> Michael Thomas <mat@cisco.com> writes:
> 
> > I'm still willing to edit the draft if we're not
> > talking about wholesale changes, and we're talking
> > about a relatively modest amount of time (eg, a 
> > few months). 
> 
> I hope it'll only take a few months, but I know Sam is going to be a
> stickler for quality before the IESG.  This isn't a bad thing, but I
> think it's going to put a lot more scrutiny on the document, so it may
> be significantly more work than you expect at the moment.  It's hard
> to say right now.
> 
> At the face of it we need to update the document to meet the new
> format requirements, update to krb-clarifications and krb-crypto, and
> probably update to reference IKEv2 and 2401bis.  I dont know what
> other changes are going to be required.
> 

I think I missed something: Why do we need to update to reference ikev2? The
ikev1 phase 2 exchange works just fine.

jan


> So, if you're willing (and able) to put in the time and effort to
> remain the editor I'm happy to keep you.  However if you feel that you
> cannot commit to the task I'd ask that we find someone else.  I leave
> that choice up to you for now.
> 
> > Has a decision been made on wg meeting in MPLS?
> > I'm hoping that the issues don't require a f2f 
> > meeting, but it would be good to know one way or
> > the other.
> 
> I'm willing to go either way.  If the WG believes we need a face to
> face meeting then I'll gladly arrange for one.
> 
> > 		Mike
> 
> -derek
> 
> -- 
>        Derek Atkins                 617-623-3745
>        derek@ihtfp.com             www.ihtfp.com
>        Computer and Internet Security Consultant
> 



From owner-ietf-kink@mail.vpnc.org  Thu Jan 20 06:10:09 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16630
	for <kink-archive@lists.ietf.org>; Thu, 20 Jan 2005 06:10:08 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KB4pDY084769;
	Thu, 20 Jan 2005 03:04:51 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0KB4pjp084767;
	Thu, 20 Jan 2005 03:04:51 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from march.taca.jp (vbox.nezu.wide.ad.jp [203.178.142.195])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KB4g71084573
	for <ietf-kink@vpnc.org>; Thu, 20 Jan 2005 03:04:42 -0800 (PST)
	(envelope-from nov@tahi.org)
Received: from localhost (vbox.nezu.wide.ad.jp [203.178.142.195])
	by march.taca.jp (Postfix) with ESMTP
	id 51C301FBC2; Thu, 20 Jan 2005 20:04:41 +0900 (JST)
Date: Thu, 20 Jan 2005 20:04:41 +0900 (JST)
Message-Id: <20050120.200441.92259087.nov@tahi.org>
To: vilhuber@cisco.com
Cc: derek@ihtfp.com, mat@cisco.com, sakane@kame.net, ietf-kink@vpnc.org
Subject: Re: who will edit the draft ?
From: Nobuo OKABE <nov@tahi.org>
In-Reply-To: <Pine.LNX.4.61.0501192022390.8184@mediapc.goinhome.com>
References: <1106185907.2953.37.camel@thomasm-lnx.cisco.com>
	<sjm651syi02.fsf@dogbert.ihtfp.org>
	<Pine.LNX.4.61.0501192022390.8184@mediapc.goinhome.com>
X-Mailer: Mew version 4.1 on Emacs 20.7 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


From: Jan Vilhuber <vilhuber@cisco.com>
Subject: Re: who will edit the draft ?
Date: Wed, 19 Jan 2005 20:23:34 -0800 (PST)

> > At the face of it we need to update the document to meet the new
> > format requirements, update to krb-clarifications and krb-crypto, and
> > probably update to reference IKEv2 and 2401bis.  I dont know what
> > other changes are going to be required.
> 
> I think I missed something: Why do we need to update to reference ikev2? The
> ikev1 phase 2 exchange works just fine.

Sam should be the right person to answer the question.

However, I guess his mind .......
the point might be not the functionality of KINK
but consistency among standards issued by IETF.

I also guess that this issue might not be raised
if KINK draft fixed earlier because IKEv2 and 2401bis
were far from mature.

----- nobuo



From owner-ietf-kink@mail.vpnc.org  Thu Jan 20 11:18:37 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10478
	for <kink-archive@lists.ietf.org>; Thu, 20 Jan 2005 11:18:35 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KGD31U072674;
	Thu, 20 Jan 2005 08:13:03 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0KGD3mu072673;
	Thu, 20 Jan 2005 08:13:03 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from sj-iport-2.cisco.com (sj-iport-2-in.cisco.com [171.71.176.71])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KGD00E072605
	for <ietf-kink@vpnc.org>; Thu, 20 Jan 2005 08:13:00 -0800 (PST)
	(envelope-from mat@cisco.com)
Received: from sj-core-1.cisco.com (171.71.177.237)
  by sj-iport-2.cisco.com with ESMTP; 20 Jan 2005 08:17:40 -0800
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j0KGCdM8001986;
	Thu, 20 Jan 2005 08:12:39 -0800 (PST)
Received: from thomasm-lnx.cisco.com (thomasm-lnx.cisco.com [171.71.96.50])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j0KG9JnT000601;
	Thu, 20 Jan 2005 08:09:19 -0800
Subject: Re: who will edit the draft ?
From: Michael Thomas <mat@cisco.com>
To: Jan Vilhuber <vilhuber@cisco.com>
Cc: Derek Atkins <derek@ihtfp.com>, Shoichi Sakane <sakane@kame.net>,
        ietf-kink@vpnc.org
In-Reply-To: <Pine.LNX.4.61.0501192022390.8184@mediapc.goinhome.com>
References: <20050120102450Q.sakane@kame.net>
	 <1106185907.2953.37.camel@thomasm-lnx.cisco.com>
	 <sjm651syi02.fsf@dogbert.ihtfp.org>
	 <Pine.LNX.4.61.0501192022390.8184@mediapc.goinhome.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-zetGwP+oQK2A8cUZjKXh"
Organization: Cisco Systems
Message-Id: <1106237569.2953.40.camel@thomasm-lnx.cisco.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 
Date: Thu, 20 Jan 2005 08:12:49 -0800
IIM-SIG: v:"1.1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1106237359.544438"; x:"432200"; a:"rsa-sha1"; b:"nofws:888";
	e:"Iw=="; n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2p"
	"XIweAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRUtW+c43sl9jC"
	"50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"n8AoJOkWzxApA4Z/NsJdjDcv2JM5WtaDdyNWEI+zScWdCeJu+Nr9U5ExT2QuC54fmPZRGJXe"
	"jJDfTgoMqJmcWTVlKP+DJxQeZ71Nm3YHpY+2CowLT1rI+rpazXXsvc0rR+5FjEpp1AtHJYqugat"
	"AMSZaBl4HvmN1vUheymbhv8g=";
	c:"Subject: Re: who will edit the draft ?";
	c:"From: Michael Thomas <mat@cisco.com>";
	c:"Date: Thu, 20 Jan 2005 08:12:49 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>



--=-zetGwP+oQK2A8cUZjKXh
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Wed, 2005-01-19 at 20:23, Jan Vilhuber wrote:

> I think I missed something: Why do we need to update to reference ikev2? =
The
> ikev1 phase 2 exchange works just fine.

A reasonable question. Were there any changes to
quick mode/phase 2/sa establishment payloads in
ikev2? I didn't pay much attention to that part of
the effort, but I vaguely remember that they formalized
some of the selector stuff, maybe involving port
ranges or something??

		Mike

--=-zetGwP+oQK2A8cUZjKXh
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iQCVAwUAQe/YgbMsDAj/Eq++AQLZOgQAidbikXVTsV3l4tpazBdtBGy3U7rsLaMb
GrBMjVGGuMcsxk51QbSuO/ugwDpmAF8B9zxIgUYRXWkgrhpHv9Ob/Qmj5cz3R/pB
IByAsN3zUi+bQUxyvJEDi3sZaJzos+i16SbEoETZbMwEHXD89vb6Srv9rfjSNVVg
gcmbi5so46w=
=nHlQ
-----END PGP SIGNATURE-----

--=-zetGwP+oQK2A8cUZjKXh--



From owner-ietf-kink@mail.vpnc.org  Thu Jan 20 11:22:09 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10746
	for <kink-archive@lists.ietf.org>; Thu, 20 Jan 2005 11:22:08 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KGJfI5077851;
	Thu, 20 Jan 2005 08:19:41 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0KGJf0M077850;
	Thu, 20 Jan 2005 08:19:41 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from cz.mit.edu (CARTER-ZIMMERMAN.MIT.EDU [18.18.3.197])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KGJeE2077843
	for <ietf-kink@vpnc.org>; Thu, 20 Jan 2005 08:19:40 -0800 (PST)
	(envelope-from hartmans@mit.edu)
Received: by cz.mit.edu (Postfix, from userid 8042)
	id E1D0AE0063; Thu, 20 Jan 2005 11:19:26 -0500 (EST)
To: Ken Raeburn <raeburn@mit.edu>
Cc: ietf-kink@vpnc.org
Subject: Re: AD review: draft-ietf-kink-kink [section 1-4]
References: <tslzmz65pzn.fsf@cz.mit.edu>
	<500B80B3-6A99-11D9-9F67-000A95909EE2@mit.edu>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Thu, 20 Jan 2005 11:19:26 -0500
In-Reply-To: <500B80B3-6A99-11D9-9F67-000A95909EE2@mit.edu> (Ken Raeburn's
 message of "Wed, 19 Jan 2005 23:11:08 -0500")
Message-ID: <tslk6q8cbu9.fsf@cz.mit.edu>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


>>>>> "Ken" == Ken Raeburn <raeburn@MIT.EDU> writes:

    Ken> On Jan 18, 2005, at 17:31, Sam Hartman wrote:
    >> Kerberos is now using the term user-user rather than
    >> user-to-user.

    Ken> You've got this backwards, Sam.  Both RFC 1510 and
    Ken> draft-ietf-krb-wg-kerberos-clarifications use "user-to-user".

Yeah.  KINK uses user-user; Kerberos uses user-to-user.  My comment
was confused.



From owner-ietf-kink@mail.vpnc.org  Thu Jan 20 11:23:14 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10845
	for <kink-archive@lists.ietf.org>; Thu, 20 Jan 2005 11:23:14 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KGM4to079066;
	Thu, 20 Jan 2005 08:22:04 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0KGM4Kg079065;
	Thu, 20 Jan 2005 08:22:04 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from cz.mit.edu (CARTER-ZIMMERMAN.MIT.EDU [18.18.3.197])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KGM44X079056
	for <ietf-kink@vpnc.org>; Thu, 20 Jan 2005 08:22:04 -0800 (PST)
	(envelope-from hartmans@mit.edu)
Received: by cz.mit.edu (Postfix, from userid 8042)
	id DE1D4E0063; Thu, 20 Jan 2005 11:22:04 -0500 (EST)
To: Nobuo OKABE <nov@tahi.org>
Cc: ietf-kink@vpnc.org
Subject: Re: AD review: draft-ietf-kink-kink [section 1-4]
References: <tslzmz65pzn.fsf@cz.mit.edu>
	<20050120.102207.68299999.nov@tahi.org>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Thu, 20 Jan 2005 11:22:04 -0500
In-Reply-To: <20050120.102207.68299999.nov@tahi.org> (Nobuo OKABE's message
 of "Thu, 20 Jan 2005 10:22:07 +0900 (JST)")
Message-ID: <tslfz0wcbpv.fsf@cz.mit.edu>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


>>>>> "Nobuo" == Nobuo OKABE <nov@tahi.org> writes:

    Nobuo> It seems fair to me to postpone the date of fixing the
    Nobuo> milestones from February 7 to after IETF62.  Because the
    Nobuo> progress of 1401bis has impact against the KINK draft.

I'm uncomfortable with doing this.  I think that we can set deadlines
now.  If we find interesting new facts we can change the deadlines.

I'll listen to concerns from the chairs if they believe they will not
be able to get milestones ready by February 7 and evaluate those
concerns.

--Sam



From owner-ietf-kink@mail.vpnc.org  Thu Jan 20 11:34:53 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12908
	for <kink-archive@lists.ietf.org>; Thu, 20 Jan 2005 11:34:53 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KGXLFb086800;
	Thu, 20 Jan 2005 08:33:21 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0KGXLX4086799;
	Thu, 20 Jan 2005 08:33:21 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KGXGgU086635
	for <ietf-kink@vpnc.org>; Thu, 20 Jan 2005 08:33:16 -0800 (PST)
	(envelope-from mat@cisco.com)
Received: from sj-core-5.cisco.com (171.71.177.238)
  by sj-iport-3.cisco.com with ESMTP; 20 Jan 2005 09:40:59 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j0KGX8Nt004158;
	Thu, 20 Jan 2005 08:33:09 -0800 (PST)
Received: from thomasm-lnx.cisco.com (thomasm-lnx.cisco.com [171.71.96.50])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j0KGTb53000835;
	Thu, 20 Jan 2005 08:29:37 -0800
Subject: Re: KINK should referenece to IKEv2?
From: Michael Thomas <mat@cisco.com>
To: Shoichi Sakane <sakane@kame.net>
Cc: ietf-kink@vpnc.org
In-Reply-To: <20050120122017V.sakane@kame.net>
References: <41EF17D7.4060108@miyazawa.org>
	 <20050120122017V.sakane@kame.net>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-6lKuB9BZnxBJimVYNr/S"
Organization: Cisco Systems
Message-Id: <1106238787.2951.51.camel@thomasm-lnx.cisco.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 
Date: Thu, 20 Jan 2005 08:33:07 -0800
IIM-SIG: v:"1.1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1106238577.769859"; x:"432200"; a:"rsa-sha1"; b:"nofws:1756";
	e:"Iw=="; n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2p"
	"XIweAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRUtW+c43sl9jC"
	"50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"X0F22zBTO7qL6J9QEwleslP41N5EDXfcMYyJrcdjij6tzuG0oL9Xp/ObK/bvISoMZOF+qjkz"
	"BH2O6p+tK9VawhrVIUuJ/JiK3O+wILDjNYiZa3GCccjQI9zJtUdbhfBAqlYbnjf+cdb9aeb5pj8"
	"pYJOgbnwyAVupnK3EU++ZZQM=";
	c:"Subject: Re: KINK should referenece to IKEv2?";
	c:"From: Michael Thomas <mat@cisco.com>";
	c:"Date: Thu, 20 Jan 2005 08:33:07 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>



--=-6lKuB9BZnxBJimVYNr/S
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Wed, 2005-01-19 at 19:20, Shoichi Sakane wrote:
> > > In my opinion from reading the minutes at the IETF50 minneapolis,
> > > there is no strict reason to change the referenece from IKEv1 to IKEv=
2
> > > because the ISAKMP payload in the KINK is just used to carry a set of
> > > IPsec parameters, and Notification Payloads.
>=20
> > We should have a consensus whether we will discuss KINK based on rfc240=
1bis
> > or rfc2401.
>=20
> Well I put on a KINK hat, if the KINK specification will conform to
> rfc2401bis and if the KINK won't work on the stack based on *RFC2401*,
> we won't be happy because it will take long time to deploy the stack
> based on rfc2401bis.  so we need to implement a stack based on rfc2401bis
> first before we will run a KINK function.
>=20
> so we can have four choices while researching the difference between
> 2401bis and RFC2401 from KINK requirement of view:
>=20
> 	1. make a standard base on both rfc2401 and IKEv1.
> 	2. make a standard base on both rfc2401 and IKEv2.
> 	3. make a standard base on both 2401bis and IKEv1.
> 	4. make a standard base on both 2401bis and IKEv2.
>=20
> I would like #1 then we proceed to #4.

Somebody will need to help me (us) here: can
IKEv1 successfully establish 2401bis SA's? Can
IKEv2 successfully establish 2401 SA's? I'm _guessing_
that the answer to both is "yes", but the big question
is whether there's anything in IKEv2 what is exchanged
across the wire to inform the other side whether it's
2401 or 2401bis. If so, we may need a similar mechanism.

		Mike=20

--=-6lKuB9BZnxBJimVYNr/S
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iQCVAwUAQe/dQ7MsDAj/Eq++AQJTNgP7BmifzxPdu4DYq/UQhaWSf6tV4jb8ier6
OVAWJ1/y1CZgBRuf+toHKZczuG32XTHQu89zKNgNm0slQtYDp1TTlqvnPe2fcBf3
BJ9+q0GtdcUQ5fQlqZtxW0WeU3zofP+FrO+2ZxnCsL+cyXYLcSCbS2Biuump/wVg
/FtzaNlyDp8=
=FgzP
-----END PGP SIGNATURE-----

--=-6lKuB9BZnxBJimVYNr/S--



From owner-ietf-kink@mail.vpnc.org  Thu Jan 20 12:05:07 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15673
	for <kink-archive@lists.ietf.org>; Thu, 20 Jan 2005 12:05:06 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KGvfhR006325;
	Thu, 20 Jan 2005 08:57:41 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0KGvfFZ006324;
	Thu, 20 Jan 2005 08:57:41 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KGvfIX006269
	for <ietf-kink@vpnc.org>; Thu, 20 Jan 2005 08:57:41 -0800 (PST)
	(envelope-from mat@cisco.com)
Received: from sj-core-2.cisco.com (171.71.177.254)
  by sj-iport-3.cisco.com with ESMTP; 20 Jan 2005 10:05:23 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j0KGvTl2001816;
	Thu, 20 Jan 2005 08:57:30 -0800 (PST)
Received: from thomasm-lnx.cisco.com (thomasm-lnx.cisco.com [171.71.96.50])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j0KGs2Uk001121;
	Thu, 20 Jan 2005 08:54:02 -0800
Subject: Re: AD review: draft-ietf-kink-kink [section 1-4]
From: Michael Thomas <mat@cisco.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Cc: ietf-kink@vpnc.org
In-Reply-To: <tslzmz65pzn.fsf@cz.mit.edu>
References: <tslzmz65pzn.fsf@cz.mit.edu>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Af8YAjAHftCfFBwI9GJi"
Organization: Cisco Systems
Message-Id: <1106240252.2951.65.camel@thomasm-lnx.cisco.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 
Date: Thu, 20 Jan 2005 08:57:32 -0800
IIM-SIG: v:"1.1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1106240042.645389"; x:"432200"; a:"rsa-sha1"; b:"nofws:1727";
	e:"Iw=="; n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2p"
	"XIweAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRUtW+c43sl9jC"
	"50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"YYlsiCOhG+DQtH1Z4DITsSvW61iMnF/frA0C4YisW6DuMIF2/CARwE97dYrryqkWZHAEz7/4"
	"Z/Lb2Ho8n8FLxt4L+REyCHoEY3uNxpkE0BJnxHvYcPrMhx4vSUNZ5y1aAjutLJp+yxIMo7IIXEQ"
	"qNp/SxPDilvsBZnjuV2EXwrg=";
	c:"Subject: Re: AD review: draft-ietf-kink-kink [section 1-4]";
	c:"From: Michael Thomas <mat@cisco.com>";
	c:"Date: Thu, 20 Jan 2005 08:57:32 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>



--=-Af8YAjAHftCfFBwI9GJi
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2005-01-18 at 14:31, Sam Hartman wrote:

> Section 4.4
>=20
> IPsec does not allow half-open security associations any more as far
> as I can tell in 2401bis.  So it's not just for simplicity, but for
> model conformance.

Where is this "model conformance"? This is a kernel=20
level suggestion at best, and if 2401bis forbids this,
nothing actually changes with the KINK protocol except
for the fact that it loses data which isn't KINK's fault,
but 2401bis' notion of "conformance". In any case, I=20
don't see why we should change this especially since 2401
isn't broken in this way.

> Section 4.4.1:
>=20
> Please make sure this discussion is aligned with 2401bis.  I think it
> may change small details but they seem to have adopted much of the
> same strategy kink uses.  The area wher I believe they speak to this
> issue is when you should rekey (timers etc)

This is a classic case of KINK being the _actual_ start
of IKEv2 and 2401bis. The main question I have is whether
there is something _wrong_ here. I really don't think it's
fair to just be sending us off on work assignments if there's
no reason to believe that what the draft states is incorrect.

> Section 4.4.2
>=20
> [**] Discuss status message, rebooting peers and u2u.  This looks a
> lot like the IKE case where you lose all cryptographic context to me.

I don't understand what you want here. Are you saying that
this doesn't work in the u-u case? I don't understand what
u-u has to do with anything here.

		Mike

--=-Af8YAjAHftCfFBwI9GJi
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iQCVAwUAQe/i/LMsDAj/Eq++AQINcwQAr9mPC+txhiTEVYNjefikRtUKc9hbWQZA
FlrdMRN+LBHzjhZgCGQ38/zExWOhO/86DZrgajuZAxQEotcioKkONJq8C3bNAPXd
qYRRaBQMBeglo1pbHUyldMOFOwC12O5rSIQ6AOxjJ3cbFWnjW9CWKtcW8Jv7glQn
lUNFYDbKNm8=
=3/Pw
-----END PGP SIGNATURE-----

--=-Af8YAjAHftCfFBwI9GJi--



From owner-ietf-kink@mail.vpnc.org  Thu Jan 20 13:20:22 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21654
	for <kink-archive@lists.ietf.org>; Thu, 20 Jan 2005 13:20:19 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KIBGlq044505;
	Thu, 20 Jan 2005 10:11:16 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0KIBGMo044504;
	Thu, 20 Jan 2005 10:11:16 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KIBFaW044450
	for <ietf-kink@vpnc.org>; Thu, 20 Jan 2005 10:11:15 -0800 (PST)
	(envelope-from mat@cisco.com)
Received: from sj-core-5.cisco.com (171.71.177.238)
  by sj-iport-3.cisco.com with ESMTP; 20 Jan 2005 11:18:56 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id j0KIB6Nt027464;
	Thu, 20 Jan 2005 10:11:06 -0800 (PST)
Received: from thomasm-lnx.cisco.com (thomasm-lnx.cisco.com [171.71.96.50])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j0KI7ZQH001934;
	Thu, 20 Jan 2005 10:07:35 -0800
Subject: Re: KINK issue list
From: Michael Thomas <mat@cisco.com>
To: "KAMADA Ken'ichi" <kamada@nanohz.org>
Cc: ietf-kink@vpnc.org
In-Reply-To: <20050120110448RR%kamada@nanohz.org>
References: <20050120102450Q.sakane@kame.net>
	 <20050120103639RZ%kamada@nanohz.org>  <20050120110448RR%kamada@nanohz.org>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-oL4zK1LYeSOvSM3ym4mC"
Organization: Cisco Systems
Message-Id: <1106244665.2953.78.camel@thomasm-lnx.cisco.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 
Date: Thu, 20 Jan 2005 10:11:05 -0800
IIM-SIG: v:"1.1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1106244455.146060"; x:"432200"; a:"rsa-sha1"; b:"nofws:10365";
	e:"Iw=="; n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2p"
	"XIweAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRUtW+c43sl9jC"
	"50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"Ulh0D+7AIztbbWnAM8SC1NobTjDIypKzI7HjOhn6yHMerdvO6fhBeK6+pBmP8HihN0tz5dHK"
	"qUaxcTvwfmJO4PMDk3XIYiNO+cZWScYjkDNIAH0pDdl7hlCHDH2t9Cn82yHrKq/YJYqsc3jx2NJ"
	"+ENpaq75srhOOvSTb4mylHeY=";
	c:"Subject: Re: KINK issue list";
	c:"From: Michael Thomas <mat@cisco.com>";
	c:"Date: Thu, 20 Jan 2005 10:11:05 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>



--=-oL4zK1LYeSOvSM3ym4mC
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Thank you very much for compiling this list -- I have
been having a hard time following what are similar or the
same issues, and what the closure is if any. Maybe what
we can do is keep a master list here, the proposed=20
resolution, or whether to close the issue due to it being
not a problem. From that, I can work on producing a new
draft.

		Mike=20

On Wed, 2005-01-19 at 18:04, KAMADA Ken'ichi wrote:
> Here is a merged version of KINK issues expressed till now.
> If I missed some of them you noted, please let me know.
>=20
>=20
> [**] Indicates an issue considered substantive.
> [-] Indicates an editorial issue.
>=20
>=20
> [**] user-to-user (section 3 and 4.2)
>=20
> 	It seems like the
> 	server tells the client what principal to authenticate to, but this
> 	principal is not properly authorized.  (Sam Hartman)
>=20
> 	More examination of user-to-user case, especially situations where=20
> 	it might *not* be two PKINIT clients, which section 3 says is possible.=20
> 	(BTW, in the Kerberos docs, it's "user-to-user", not "user-user".)
> 	(Ken Raeburn)
>=20
> 	Verifying remotely supplied identity, as Sam raised earlier.
> 	(Ken Raeburn)
>=20
> 	In the user-to-user case with TGTs, I think the KINK draft may be=20
> 	over-specifying things that should be dealt with at the Kerberos level.=20
> 	If things are underspecified in Kerberos Clarifications, let's deal=20
> 	with that.  (Ken Raeburn)
>=20
> 	Section 4.2:
> 	[**] How will the initiator determine whether it will be able to get a
> 	TGT?  I think policy considerations of when to use u2u and
> 	authorization considerations of what u2u principals are authorized are
> 	underspecified in the draft.
> 	(Sam Hartman)
>=20
> 	[**] Make sure the descriptions of u2u work correctly in the
> 	cross-realm case.
> 	(Sam Hartman)
>=20
>=20
> [**] CREATE Security Association from the aspect of 2401bis (section 4.3)
>=20
> 	[**] I need explicit review from the IPsec reviewer of this section to
> 	make sure it is compatible with 2401bis.  IN addition, any differences
> 	between how this works and how IKE would set up the same SA need to be
> 	called out.  It is fine for there to be differences, but I want to
> 	make sure the working group explicitly decided the differences are a
> 	good thing.
>=20
> 	I'm somewhat concerned that 4.3 is not specific enough to describe
> 	exactly what key gets set up.  I.E. I'm concerned it may not be
> 	detailed enough for interoperable implementations.
> 	(Sam Hartman)
>=20
>=20
> [*] When 3-way, is responder's nonce MUST or SHOULD? (section 4.3 and 7.3=
)
>=20
> 	Sec 4.3 and 7.3 use SHOULD and MUST respectively regarding when the=20
> 	nonce should be used.  If the circumstances they're describing are=20
> 	different, that's okay, but if so, I missed it on first reading.
> 	(Ken Raeburn)
>=20
>=20
> [*] Half open (section 4.4)
>=20
> 	IPsec does not allow half-open security associations any more as far
> 	as I can tell in 2401bis.  So it's not just for simplicity, but for
> 	model conformance.  (Sam Hartman)
>=20
>=20
> [**] Section 4.4.2
>=20
> 	[**] Discuss status message, rebooting peers and u2u.  This looks a
> 	lot like the IKE case where you lose all cryptographic context to me.
>=20
>=20
> [*] CksumLen (section 5)
>=20
> 	Diagram indicates one octet for cksumlen, but the text (and=20
> 	kcrypto specifications) say it should be two.
>=20
>=20
> [**] etype does not directly indicate checksum type (section 5)
>=20
> 	a key's encryption type does not directly indicate=20
> 	a checksum type, it indicates an encryption(-with-integrity-protection)=20
> 	scheme, which does include a required-to-implement checksum type
> 	(Ken Raeburn)
>=20
>=20
> [**] Kerberos allows variable length checksum (section 5)
>=20
> 	I'd have to go back and check, but I don't think we require that=20
> 	a given checksum type have a fixed output size, so "leave X amount of=20
> 	space and fill it with zero for computing the checksum" is questionable=20
> 	too.  (Ken Raeburn)
>=20
>=20
> [*] Kerberos checksum is not deterministic (section 5)
>=20
> 	The Kink description of how to verify a checksum assumes that
> 	Kerberos checksums are deterministic; this is not strictly required.
> 	(Sam Hartman)
>=20
> 	let kcrypto specify how=20
> 	to verify a checksum, as they're not required to be deterministic, so=20
> 	the "compute it again and compare" approach specified in section 5 is=20
> 	wrong  (Ken Raeburn)
>=20
> 	The spec should describe how to verify checksum as follows.
>=20
> 	To verify the checksum, the checksum is saved, and the
> 	checksum field is zeroed out.  The resulting message and the saved
> 	checksum are passed to the verification function.  If the verification
> 	fails, the message MUST be dropped.
>=20
>=20
> [*] Subsession keys (section 5 and 8)
>=20
> 	Are subsession keys ignored?  (Ken Raeburn)
>=20
>=20
> [**] Checksum when KRB-ERROR occured (section 5.1.4 and 7.1)
>=20
> 	Section 7.1 says the checksum in the KRB-ERROR message is not used,
> 	but section 5.1.4 says that KINK implementation MUST make use of
> 	keyed Kerberos errors.  But KRB-ERROR does not have checksum in it (at
> 	least with RFC 1510 or kerberos-clarifications).
> 	I think a correct phrase here is "KINK implementations MUST make use of
> 	a KINK Cksum field when returning KINK_KRB_ERROR and the appropriate
> 	service key is available."
>=20
>=20
> [**] KINK_ENCRYPT format (section 5.1.8)
>=20
> 	The format of the encrypted part of KINK_ENCRYPT (section 5.1.8) is
> 	vague.  I think of using the output of raw encryption algorithms
> 	(i.e. E(confounder | plaintext | pad)) or using EncryptedData.
>=20
> 	treat "encryption with=20
> 	integrity protection" output as a whole, don't peek under the covers to=20
> 	find a "checksum" part you can throw away  (Ken Raeburn)
>=20
> 	drop references to the initialization vector  (Ken Raeburn)
>=20
>=20
> [*] Kerberos PFS (section 6.8)
>=20
> 	Sec 6.8: "Kerberos in general does not provide FPS so it is somewhat=20
> 	questionable whether a system which is heavily relying on Kerberos=20
> 	benefits from PFS."  First, that sounds like it might be Security=20
> 	Considerations material.  Second, I don't follow; explain please?
> 	(Ken Raeburn)
>=20
>=20
> [*] MUST/SHOULD in clock skew (section 7.1)
>=20
> 	The time difference MUST be computed and SHOULD be stored=20
> 	and used?  Why the different requirement levels?  (And is this sort of=20
> 	thing in the domain of KINK or Kerberos?)  (Ken Raeburn)
>=20
>=20
> [**] prf (section 8)
>=20
> 	Section 8 says "prf is the same hash algorithm found in the session
> 	ticket's etype", but krb-wg-crypto-07 defines hash as unkeyed.
> 	Fortunately krb-wg-crypto-07 defines a PRF for each etype, so KINK
> 	should use this PRF.
>=20
> 	Use a prf=20
> 	from kcrypto, don't assume the checksum operations are deterministic=20
> 	hash functions  (Ken Raeburn)
>=20
>=20
>=20
> [*] Key derivation (section 8)
>=20
> 	The key derivation seems inconsistent with the crypto framework
> 	document.  (Sam Hartman)
>=20
>=20
> [*] Key usage
>=20
> 	Usage of  kink should specify the key usage numbers for kerberos
> 	encryption.  (Sam Hartman)
>=20
>=20
> [*] 2401bis
>=20
> 	section 4.4.1:
> 	Please make sure this discussion is aligned with 2401bis.  I think it
> 	may change small details but they seem to have adopted much of the
> 	same strategy kink uses.  The area wher I believe they speak to this
> 	issue is when you should rekey (timers etc)
>=20
>=20
> [*] IKEv2
>=20
> 	Should we adopt IKEv2?
>=20
> 	If we should...
> 	- IKEv2 does not have DOI, so how to handle the DOI field in the KINK
> 	  packet header should be described.
> 	- Use TS (Traffic Selector) instead of ID (Identification).
> 	- KEYMAT calculation is changed.
> 	- How to handle REKEY_SA Notify type.
>=20
>=20
> [*] behavior on KINK_ERROR
>=20
> 	In implementor's point of view, I'd like to see initiator's
> 	behavior in receiving KINK_ERROR to be defined.
> 	For example:
> 	- When KINK_OK is received, initiator MAY act as if the KINK_ERROR
> 	  payload was not included in the messaged.
> 	- When KINK_BADQMVERS is received and the Cksum is verified,
> 	  initiator MAY retry in other Quick Mode version.
> 	- When one of other error codes is received and the Cksum is verified,
> 	  initiator SHOULD abort the negotiation.
>=20
>=20
> [-] I-D nits
>=20
> 	Review the I-D nits and RFC authors docs.  I spotted a lot of=20
> 	mechanical things (number of lines per page; avoid hyphenation; use=20
> 	ragged right margin; need two spaces after sentence-ending period; fix=20
> 	page numbers in table of contents; add section numbers to TOC) most of=20
> 	which I think are specified in one of those documents.
> 	(Ken Raeburn)
>=20
> 	the document needs to meet all the ID nits when it is
> 	submitted.  (Sam Hartman)
>=20
>=20
> [-] IANA considerations
>=20
> 	I think the correct terminology is "port=20
> 	number", not "port", and they're "assigned", not "created".  This=20
> 	section says no new registries are required in the first paragraph, and=20
> 	the third one specifies that IANA must create one (but without the=20
> 	associated procedural data that is required nowadays).  Are the KINK=20
> 	payload types and ISAKMP payload types actually ever used in the same=20
> 	field?  If not, I don't think they need to come out of the same=20
> 	registry.  (Ken Raeburn)
>=20
>=20
> [-] Wording/Terminology
>=20
> 	Section 2 and 10.1.
> 	Kerberos is now using the term user-user rather than user-to-user.
> 	(Sam Hartman)
>=20
> 	Section 2.
> 	Principals are not either client or service principals;
> 	they can and often do fill both roles.  (Sam Hartman)
>=20
> 	Section 2, last paragraph.  "Between" is generally non-directional,=20
> 	but in this case, a direction seems to be intended to be inferred; try=20
> 	"from...to" instead.  (Ken Raeburn)
>=20
> 	Section 3, English usage/grammar problems with the first two paragraphs.
> 	(Sam Hartman)
>=20
> 	Section 3.
> 	   which allows a final acknowledgment message when the respondent needs
> 	   a full three-way handshake. This is only needed when the optimistic
> 	   keying route is not taken, though it is expected that that will not
> 	   be the norm. KINK also provides rekeying and dead peer detection as
> 	What is expected not to be the norm?  Please reword.
> 	(Sam Hartman)
>=20
> 	Section 4.3, discussing attributes, mixes singular and plural=20
> 	indications.  The word "lone" appears to be popular with the author,=20
> 	too. :-)  (Ken Raeburn)
>=20
> 	Sec 8: "By optional, it is meant..." is badly worded.  (Ken Raeburn)
>=20
>=20
> [-] References
>=20
> 	The reference to [PKCROSS] is unnecessary, and only happens once, in=20
> 	the introduction.  I'd suggest dropping it.  That's one less=20
> 	unpublished I-D in the references section.  (Ken Raeburn)
>=20
> 	[KRBREVS] is referenced but not listed in the references section.
> 	(Ken Raeburn)
>=20
> 	Sec 5.1.7, next to last paragraph on page 21, is "IKE" (the=20
> 	protocol) fuzzy about use of different SAs, or is it "[IKE]" (the=20
> 	document)?  (Ken Raeburn)
>=20
> 	Section 1:
> 	Remove the reference to pkcross or cite something outside the IETF.
> 	It's an expired ID without and active editor.  (Sam Hartman)
>=20
> 	Section 1:
> 	Add an informative reference to IKE.  (Sam Hartman)
>=20
> 	Section 2:
> 	Cite a reference for DER.  (Sam Hartman)
>=20
>=20
> [-] Typos
>=20
> 	4.4.2. Dead Peer Detection
> 	In the fourth paragraph, "loose" is to be "lose".
>=20
> 	5.1.1. KINK Padding Rules
> 	In the second item, "other other" is to be "other".
>=20
> 	5.1.1. KINK Padding Rules
> 	The first item in the list should end with a period like=20
> 	the others.  (Ken Raeburn)
>=20
> 	5.1.5. KINK_TGT_REQ Payload
> 	In the third item, "krbtgt/REALM/@REALM" is to be "krbtgt/REALM@REALM".
>=20
> 	5.1.6. KINK_TGT_REP Payload
> 	In the caption of Figure 13, "KINK_TGT_REQ" is to be "KINK_TGT_REP".
>=20
> 	7.3. CREATE
> 	"IPspec" is to be "IPsec".
>=20
> 	7.5. STATUS
> 	In the last paragraph, "REPLY KINK Header" should be in one line.
> 	In the last paragraph, "[KRB_ERROR]" is to be "[KINK_ERROR]".
>=20
> 	overall:
> 	"'s" is used in some places where I'd use "s" for a plural form.
>=20

--=-oL4zK1LYeSOvSM3ym4mC
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iQCVAwUAQe/0ObMsDAj/Eq++AQKyVQP/SYy7InTgSviTkwj5zD3cCuhJoCY59Ejv
31NIJ2XJXVZNiTjETUx5T+x60YMczai+hCvNK6mJCiD8s3Z9DnlyOkXa6q7a4NkQ
Tf+ornB+ZcSS2WOX0O/judmbK2UcHcI3y5sK4CfvNXlrYzUzP3hHfz10nCUnk48d
UjELuRGAxL4=
=b3OQ
-----END PGP SIGNATURE-----

--=-oL4zK1LYeSOvSM3ym4mC--



From owner-ietf-kink@mail.vpnc.org  Thu Jan 20 14:25:57 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27435
	for <kink-archive@lists.ietf.org>; Thu, 20 Jan 2005 14:25:57 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KJK3Uu016947;
	Thu, 20 Jan 2005 11:20:03 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0KJK3C3016946;
	Thu, 20 Jan 2005 11:20:03 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from cz.mit.edu (CARTER-ZIMMERMAN.MIT.EDU [18.18.3.197])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KJK2Wk016931
	for <ietf-kink@vpnc.org>; Thu, 20 Jan 2005 11:20:02 -0800 (PST)
	(envelope-from hartmans@mit.edu)
Received: by cz.mit.edu (Postfix, from userid 8042)
	id C59A9E0063; Thu, 20 Jan 2005 14:20:02 -0500 (EST)
To: Michael Thomas <mat@cisco.com>
Cc: ietf-kink@vpnc.org
Subject: Re: AD review: draft-ietf-kink-kink [section 1-4]
References: <tslzmz65pzn.fsf@cz.mit.edu>
	<1106240252.2951.65.camel@thomasm-lnx.cisco.com>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Thu, 20 Jan 2005 14:20:02 -0500
In-Reply-To: <1106240252.2951.65.camel@thomasm-lnx.cisco.com> (Michael
 Thomas's message of "Thu, 20 Jan 2005 08:57:32 -0800")
Message-ID: <tslu0pbc3h9.fsf@cz.mit.edu>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


>>>>> "Michael" == Michael Thomas <mat@cisco.com> writes:

    Michael> On Tue, 2005-01-18 at 14:31, Sam Hartman wrote:
    >> Section 4.4
    >> 
    >> IPsec does not allow half-open security associations any more
    >> as far as I can tell in 2401bis.  So it's not just for
    >> simplicity, but for model conformance.

    Michael> Where is this "model conformance"? This is a kernel level
    Michael> suggestion at best, and if 2401bis forbids this, nothing
    Michael> actually changes with the KINK protocol except for the
    Michael> fact that it loses data which isn't KINK's fault, but
    Michael> 2401bis' notion of "conformance". 

I do not understand this sentence.  What I was trying to say is that
there may now be additional reasons having to do with 2401bis that
kink does not allow half open security associations.
I'd like the text to reflect this.

I believe the easiest way to do this is to drop the phrase "for simplicity."

    Michael> In any case, I don't
    Michael> see why we should change this especially since 2401 isn't
    Michael> broken in this way.

I believe it is important that IETF specs be clear.  If you claim that
you do something like disallow one-way SAs for simplicity, then it
needs to be true that you had an option in the matter.  As it stands,
I believe your behavior will be dictated by 2401bis.

    >> Section 4.4.1:
    >> 
    >> Please make sure this discussion is aligned with 2401bis.  I
    >> think it may change small details but they seem to have adopted
    >> much of the same strategy kink uses.  The area wher I believe
    >> they speak to this issue is when you should rekey (timers etc)

    Michael> This is a classic case of KINK being the _actual_ start
    Michael> of IKEv2 and 2401bis. The main question I have is whether
    Michael> there is something _wrong_ here. 

I do not believe there is something wrong at the protocol, although I
believe it is important to confirm that is the case.  I believe there
may be small textual alignment issues.

    Michael> I really don't think
    Michael> it's fair to just be sending us off on work assignments
    Michael> if there's no reason to believe that what the draft
    Michael> states is incorrect.


I'd like to draw your attention to section 6.7 of RFC 2418, working
group procedures:

  6.7. Area Director

     Area Directors are responsible for ensuring that working groups in
        their area produce coherent, coordinated, architecturally consistent
           and timely output as a contribution to the overall results of the
              IETF.

As part of my responsibility for producing coordinated specifications
I'm asking that the Kink draft be coordinated with RFC 2401bis.  In
particular when I notice that the Kink draft discusses the same issue
as 2401bis, I will either determine that both documents are consistent
myself or ask someone else to do so.  A response to such a question
could be of the form "I looked at the text dealing with rekeying in
2401bis; it says foo.  I Looked at kink which says barr.  These are
consistent."  A more abbreviated response of "I looked at rekeying in
2401bis and Kink and they are consistent," is appropriate in some
circumstances.

If you object to me delegating part of this review to the working
group rather than doing it all myself, I think we have a fundamental
disagreement.  I'm fairly sure that is within the set of things it is
appropriate and reasonable for me to do as an AD.

If you are concerned that you personally don't want to do all this
alignment checking, then work with the chairs to see if someone else
does.



    >> Section 4.4.2
    >> 
    >> [**] Discuss status message, rebooting peers and u2u.  This
    >> looks a lot like the IKE case where you lose all cryptographic
    >> context to me.

    Michael> I don't understand what you want here. Are you saying
    Michael> that this doesn't work in the u-u case? I don't
    Michael> understand what u-u has to do with anything here.

OK.  I was unclear .  When sending a status message, what happens if
the peer has gotten a new TGT?  How do I realize I need to use this
TGT rather than the one I have?



From owner-ietf-kink@mail.vpnc.org  Thu Jan 20 15:00:50 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29516
	for <kink-archive@lists.ietf.org>; Thu, 20 Jan 2005 15:00:50 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KJvrIT041075;
	Thu, 20 Jan 2005 11:57:53 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0KJvr5k041074;
	Thu, 20 Jan 2005 11:57:53 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from cz.mit.edu (CARTER-ZIMMERMAN.MIT.EDU [18.18.3.197])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KJvmnn041056
	for <ietf-kink@vpnc.org>; Thu, 20 Jan 2005 11:57:48 -0800 (PST)
	(envelope-from hartmans@mit.edu)
Received: by cz.mit.edu (Postfix, from userid 8042)
	id 3F318E0063; Thu, 20 Jan 2005 14:57:49 -0500 (EST)
To: Kazunori Miyazawa <kazunori@miyazawa.org>
Cc: Shoichi Sakane <sakane@kame.net>, ietf-kink@vpnc.org
Subject: Re: KINK should referenece to IKEv2?
References: <20050120111553S.sakane@kame.net> <41EF17D7.4060108@miyazawa.org>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Thu, 20 Jan 2005 14:57:49 -0500
In-Reply-To: <41EF17D7.4060108@miyazawa.org> (Kazunori Miyazawa's message of
 "Thu, 20 Jan 2005 11:30:47 +0900")
Message-ID: <tslllanc1qa.fsf@cz.mit.edu>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


>>>>> "Kazunori" == Kazunori Miyazawa <kazunori@miyazawa.org> writes:

    Kazunori> Shoichi Sakane wrote:
    >> In my opinion from reading the minutes at the IETF50
    >> minneapolis, there is no strict reason to change the referenece
    >> from IKEv1 to IKEv2 because the ISAKMP payload in the KINK is
    >> just used to carry a set of IPsec parameters, and Notification
    >> Payloads.
    >> 

    Kazunori> We should have a consensus whether we will discuss KINK
    Kazunori> based on rfc2401bis or rfc2401.


Speaking as an AD, if 2401bis is approved by IETF 62, Kink will be
based on 2401bis.  If not, then it depends on where 2401bis is, where
Kink is, and how fast things are moving.

This decision is based on the following assumptions; if these
assumptions are false the decision should be revisited.  Making Kink
based on 2401bis will not require significant change.  Making Kink
based on 2401bis will not create significant confusion for 2401
implementers.  Making kink based on 2401bis will not require
significant work for people who have mostly complete kink
implementations.

Note that I have not made the claim that kink should be based on ikev2
instead of ikev1.  I've made a related claim: the WG must come to
consensus on whether kink implements features like multiple SAs
between the same nodes that are supported by 2401bis but not 2401.  If
the working group decides not to support all the things that 2401bis
requires from ikev2, then the wg needs to explain why it made that
decision.

--Sam



From owner-ietf-kink@mail.vpnc.org  Thu Jan 20 15:05:57 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00086
	for <kink-archive@lists.ietf.org>; Thu, 20 Jan 2005 15:05:57 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KK28wr042546;
	Thu, 20 Jan 2005 12:02:08 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0KK28cn042545;
	Thu, 20 Jan 2005 12:02:08 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from cz.mit.edu (CARTER-ZIMMERMAN.MIT.EDU [18.18.3.197])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KK27g9042539
	for <ietf-kink@vpnc.org>; Thu, 20 Jan 2005 12:02:07 -0800 (PST)
	(envelope-from hartmans@mit.edu)
Received: by cz.mit.edu (Postfix, from userid 8042)
	id 4F5A1E0075; Thu, 20 Jan 2005 15:02:08 -0500 (EST)
To: Michael Thomas <mat@cisco.com>
Cc: Shoichi Sakane <sakane@kame.net>, ietf-kink@vpnc.org
Subject: Re: KINK should referenece to IKEv2?
References: <41EF17D7.4060108@miyazawa.org> <20050120122017V.sakane@kame.net>
	<1106238787.2951.51.camel@thomasm-lnx.cisco.com>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Thu, 20 Jan 2005 15:02:07 -0500
In-Reply-To: <1106238787.2951.51.camel@thomasm-lnx.cisco.com> (Michael
 Thomas's message of "Thu, 20 Jan 2005 08:33:07 -0800")
Message-ID: <tslhdlbc1j4.fsf@cz.mit.edu>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


>>>>> "Michael" == Michael Thomas <mat@cisco.com> writes:

    Michael> Somebody will need to help me (us) here: can IKEv1
    Michael> successfully establish 2401bis SA's? Can IKEv2
    Michael> successfully establish 2401 SA's? I'm _guessing_ that the
    Michael> answer to both is "yes", but the big question is whether
    Michael> there's anything in IKEv2 what is exchanged across the
    Michael> wire to inform the other side whether it's 2401 or
    Michael> 2401bis. If so, we may need a similar mechanism.

My understanding is that 2401bis supports both ikev2 and ikev1.
However 2401bis has SPD entries that cannot be satisfied by ikev1.
I.E.  2401bis allows multiple SAs to exist between the same two peers.  

There are things that ikev2 can negotiate that a pure 2401
implementation would not support.


I believe it would be OK to have an ikev2 implementation that simply
made sure not to do that.


--Sam



From owner-ietf-kink@mail.vpnc.org  Thu Jan 20 15:13:22 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01285
	for <kink-archive@lists.ietf.org>; Thu, 20 Jan 2005 15:13:21 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KKBOY7046874;
	Thu, 20 Jan 2005 12:11:24 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0KKBOda046873;
	Thu, 20 Jan 2005 12:11:24 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from cz.mit.edu (CARTER-ZIMMERMAN.MIT.EDU [18.18.3.197])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KKBNcd046867
	for <ietf-kink@vpnc.org>; Thu, 20 Jan 2005 12:11:23 -0800 (PST)
	(envelope-from hartmans@mit.edu)
Received: by cz.mit.edu (Postfix, from userid 8042)
	id 3DFA5E0077; Thu, 20 Jan 2005 15:11:24 -0500 (EST)
To: Michael Thomas <mat@cisco.com>
Cc: Shoichi Sakane <sakane@kame.net>, ietf-kink@vpnc.org
Subject: Re: who will edit the draft ?
References: <20050120102450Q.sakane@kame.net>
	<1106185907.2953.37.camel@thomasm-lnx.cisco.com>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Thu, 20 Jan 2005 15:11:24 -0500
In-Reply-To: <1106185907.2953.37.camel@thomasm-lnx.cisco.com> (Michael
 Thomas's message of "Wed, 19 Jan 2005 17:51:47 -0800")
Message-ID: <tsld5vzc13n.fsf@cz.mit.edu>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


>>>>> "Michael" == Michael Thomas <mat@cisco.com> writes:


    Michael> Has a decision been made on wg meeting in MPLS?  I'm
    Michael> hoping that the issues don't require a f2f meeting, but
    Michael> it would be good to know one way or the other.

Speaking as an individual I'd like to see an f2f meeting even if we
don't believe the issues require one.  I think it might help us get on
the same page.  Here's a proposed agenda:

* A presentation on how kcrypto differs from crypto in 1510
* A presentation on 2401bis vs 2401
* A presentation making sure we understand the difference between
     2401bis conformance   and ikev2 conformance
* Discussion of u2u and authorization
    (we may not have enough context to know whether
    we need this yet)
* A review of the issue list

I think that getting all on the same page even if we don't need f2f
time to resolve issues would benefit us.  If others disagree, then we
should not have the meeting.




From owner-ietf-kink@mail.vpnc.org  Thu Jan 20 15:14:29 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01420
	for <kink-archive@lists.ietf.org>; Thu, 20 Jan 2005 15:14:28 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KKD6uS047077;
	Thu, 20 Jan 2005 12:13:06 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0KKD6ji047076;
	Thu, 20 Jan 2005 12:13:06 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from cz.mit.edu (CARTER-ZIMMERMAN.MIT.EDU [18.18.3.197])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KKD6OG047054
	for <ietf-kink@vpnc.org>; Thu, 20 Jan 2005 12:13:06 -0800 (PST)
	(envelope-from hartmans@mit.edu)
Received: by cz.mit.edu (Postfix, from userid 8042)
	id 92555E0078; Thu, 20 Jan 2005 15:13:02 -0500 (EST)
To: Michael Thomas <mat@cisco.com>
Cc: ietf-kink@vpnc.org
Subject: Re: AD review: draft-ietf-kink-kink [section 1-4]
References: <tslzmz65pzn.fsf@cz.mit.edu>
	<1106240252.2951.65.camel@thomasm-lnx.cisco.com>
	<tslu0pbc3h9.fsf@cz.mit.edu>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Thu, 20 Jan 2005 15:13:02 -0500
In-Reply-To: <tslu0pbc3h9.fsf@cz.mit.edu> (Sam Hartman's message of "Thu, 20
 Jan 2005 14:20:02 -0500")
Message-ID: <tsl8y6nc10x.fsf@cz.mit.edu>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


>>>>> "Sam" == Sam Hartman <hartmans-ietf@mit.edu> writes:

>>>>> "Michael" == Michael Thomas <mat@cisco.com> writes:


    Sam> If you are concerned that you personally don't want to do all
    Sam> this alignment checking, then work with the chairs to see if
    Sam> someone else does.

This might have come out sounding like I was asking you to step down
as editor.  That was not my intent at all.  I simply meant that it is
reasonable to ask others to look into issues for you and if it turns
out changes need to be made then you as editor get involved.



From owner-ietf-kink@mail.vpnc.org  Thu Jan 20 15:32:10 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03216
	for <kink-archive@lists.ietf.org>; Thu, 20 Jan 2005 15:32:09 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KKRSsH060363;
	Thu, 20 Jan 2005 12:27:28 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0KKRRBB060362;
	Thu, 20 Jan 2005 12:27:27 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from cz.mit.edu (CARTER-ZIMMERMAN.MIT.EDU [18.18.3.197])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KKRIdV060037
	for <ietf-kink@vpnc.org>; Thu, 20 Jan 2005 12:27:18 -0800 (PST)
	(envelope-from hartmans@mit.edu)
Received: by cz.mit.edu (Postfix, from userid 8042)
	id 4A78CE0078; Thu, 20 Jan 2005 15:27:18 -0500 (EST)
To: Jan Vilhuber <vilhuber@cisco.com>
Cc: Derek Atkins <derek@ihtfp.com>, Michael Thomas <mat@cisco.com>,
        Shoichi Sakane <sakane@kame.net>, ietf-kink@vpnc.org
Subject: Re: who will edit the draft ?
References: <20050120102450Q.sakane@kame.net>
	<1106185907.2953.37.camel@thomasm-lnx.cisco.com>
	<sjm651syi02.fsf@dogbert.ihtfp.org>
	<Pine.LNX.4.61.0501192022390.8184@mediapc.goinhome.com>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Thu, 20 Jan 2005 15:27:17 -0500
In-Reply-To: <Pine.LNX.4.61.0501192022390.8184@mediapc.goinhome.com> (Jan
 Vilhuber's message of "Wed, 19 Jan 2005 20:23:34 -0800 (PST)")
Message-ID: <tsl4qhbalsq.fsf@cz.mit.edu>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


>>>>> "Jan" == Jan Vilhuber <vilhuber@cisco.com> writes:

    Jan> On Wed, 19 Jan 2005, Derek Atkins wrote:

    >>  Hi,
    >> 
    >> Michael Thomas <mat@cisco.com> writes:
    >> 
    >> > I'm still willing to edit the draft if we're not > talking
    >> about wholesale changes, and we're talking > about a relatively
    >> modest amount of time (eg, a > few months).
    >> 
    >> I hope it'll only take a few months, but I know Sam is going to
    >> be a stickler for quality before the IESG.  This isn't a bad
    >> thing, but I think it's going to put a lot more scrutiny on the
    >> document, so it may be significantly more work than you expect
    >> at the moment.  It's hard to say right now.
    >> 
    >> At the face of it we need to update the document to meet the
    >> new format requirements, update to krb-clarifications and
    >> krb-crypto, and probably update to reference IKEv2 and 2401bis.
    >> I dont know what other changes are going to be required.
    >> 

    Jan> I think I missed something: Why do we need to update to
    Jan> reference ikev2? The ikev1 phase 2 exchange works just fine.


I think there was confusion.  I said that you needed to reference
2401bis rather than 2401.  (I've explained the assumptions behind that
in an earlier message)

I suggested you should consider providing the additional features that
2401bis supports/requests from a key management protocol over 2401.
You should either implement these features or explain why you chose
not to do so.

How you implement these features (referencing ikev2, etc) is up to
you.



From owner-ietf-kink@mail.vpnc.org  Thu Jan 20 16:54:28 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14060
	for <kink-archive@lists.ietf.org>; Thu, 20 Jan 2005 16:54:28 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KLmqWQ082486;
	Thu, 20 Jan 2005 13:48:52 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0KLmqu2082485;
	Thu, 20 Jan 2005 13:48:52 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KLmlwG082469
	for <ietf-kink@vpnc.org>; Thu, 20 Jan 2005 13:48:47 -0800 (PST)
	(envelope-from vilhuber@cisco.com)
Received: from sj-core-2.cisco.com (171.71.177.254)
  by sj-iport-3.cisco.com with ESMTP; 20 Jan 2005 14:56:31 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from localhost (vilhuber-u30.cisco.com [128.107.162.107])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j0KLmOl3029423;
	Thu, 20 Jan 2005 13:48:25 -0800 (PST)
Date: Thu, 20 Jan 2005 13:48:36 -0800 (PST)
From: Jan Vilhuber <vilhuber@cisco.com>
X-X-Sender: vilhuber@mediapc.goinhome.com
To: Sam Hartman <hartmans-ietf@mit.edu>
cc: Derek Atkins <derek@ihtfp.com>, Michael Thomas <mat@cisco.com>,
        Shoichi Sakane <sakane@kame.net>, ietf-kink@vpnc.org
Subject: Re: who will edit the draft ?
In-Reply-To: <tsl4qhbalsq.fsf@cz.mit.edu>
Message-ID: <Pine.LNX.4.61.0501201347520.7754@mediapc.goinhome.com>
References: <20050120102450Q.sakane@kame.net> <1106185907.2953.37.camel@thomasm-lnx.cisco.com>
 <sjm651syi02.fsf@dogbert.ihtfp.org> <Pine.LNX.4.61.0501192022390.8184@mediapc.goinhome.com>
 <tsl4qhbalsq.fsf@cz.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


On Thu, 20 Jan 2005, Sam Hartman wrote:

> >>>>> "Jan" == Jan Vilhuber <vilhuber@cisco.com> writes:
> 
>     Jan> On Wed, 19 Jan 2005, Derek Atkins wrote:
> 
>     >>  Hi,
>     >> 
>     >> Michael Thomas <mat@cisco.com> writes:
>     >> 
>     >> > I'm still willing to edit the draft if we're not > talking
>     >> about wholesale changes, and we're talking > about a relatively
>     >> modest amount of time (eg, a > few months).
>     >> 
>     >> I hope it'll only take a few months, but I know Sam is going to
>     >> be a stickler for quality before the IESG.  This isn't a bad
>     >> thing, but I think it's going to put a lot more scrutiny on the
>     >> document, so it may be significantly more work than you expect
>     >> at the moment.  It's hard to say right now.
>     >> 
>     >> At the face of it we need to update the document to meet the
>     >> new format requirements, update to krb-clarifications and
>     >> krb-crypto, and probably update to reference IKEv2 and 2401bis.
>     >> I dont know what other changes are going to be required.
>     >> 
> 
>     Jan> I think I missed something: Why do we need to update to
>     Jan> reference ikev2? The ikev1 phase 2 exchange works just fine.
> 
> 
> I think there was confusion.  I said that you needed to reference
> 2401bis rather than 2401.  (I've explained the assumptions behind that
> in an earlier message)
> 
> I suggested you should consider providing the additional features that
> 2401bis supports/requests from a key management protocol over 2401.
> You should either implement these features or explain why you chose
> not to do so.
> 

I guess saying "I haven't read 2401bis" won't be a good excuse for not
implementing any features from it, is it?

jan


> How you implement these features (referencing ikev2, etc) is up to
> you.
> 



From owner-ietf-kink@mail.vpnc.org  Thu Jan 20 17:27:37 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19337
	for <kink-archive@lists.ietf.org>; Thu, 20 Jan 2005 17:27:37 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KMMEvq087284;
	Thu, 20 Jan 2005 14:22:14 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0KMMEe9087283;
	Thu, 20 Jan 2005 14:22:14 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from sj-iport-2.cisco.com (sj-iport-2-in.cisco.com [171.71.176.71])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0KMM9Qq087254
	for <ietf-kink@vpnc.org>; Thu, 20 Jan 2005 14:22:09 -0800 (PST)
	(envelope-from mat@cisco.com)
Received: from sj-core-2.cisco.com (171.71.177.254)
  by sj-iport-2.cisco.com with ESMTP; 20 Jan 2005 14:26:55 -0800
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j0KMLgl2020628;
	Thu, 20 Jan 2005 14:21:42 -0800 (PST)
Received: from thomasm-lnx.cisco.com (thomasm-lnx.cisco.com [171.71.96.50])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j0KMIT0h005026;
	Thu, 20 Jan 2005 14:18:29 -0800
Subject: Re: who will edit the draft ?
From: Michael Thomas <mat@cisco.com>
To: Jan Vilhuber <vilhuber@cisco.com>
Cc: Sam Hartman <hartmans-ietf@mit.edu>, Derek Atkins <derek@ihtfp.com>,
        Shoichi Sakane <sakane@kame.net>, ietf-kink@vpnc.org
In-Reply-To: <Pine.LNX.4.61.0501201347520.7754@mediapc.goinhome.com>
References: <20050120102450Q.sakane@kame.net>
	 <1106185907.2953.37.camel@thomasm-lnx.cisco.com>
	 <sjm651syi02.fsf@dogbert.ihtfp.org>
	 <Pine.LNX.4.61.0501192022390.8184@mediapc.goinhome.com>
	 <tsl4qhbalsq.fsf@cz.mit.edu>
	 <Pine.LNX.4.61.0501201347520.7754@mediapc.goinhome.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-LqEHyvl7gwvFgooJl54u"
Organization: Cisco Systems
Message-Id: <1106259720.2951.83.camel@thomasm-lnx.cisco.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 
Date: Thu, 20 Jan 2005 14:22:00 -0800
IIM-SIG: v:"1.1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1106259509.840722"; x:"432200"; a:"rsa-sha1"; b:"nofws:720";
	e:"Iw=="; n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2p"
	"XIweAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRUtW+c43sl9jC"
	"50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"aZb1ZNFGMPiby19TTVEo89QtdGdjSnDpjwqPpcAR0ZTp/X1ngNhDJZHYVIGSXhQuzhyrglxg"
	"AmW8XqO3pOvWjZqbAO73nb+cwFrV+bux/pVwMQ37pBnr48NMCCIgZ+qRD2IBSU7nY/FLTRx1nqx"
	"rAe4m+76u9y4KrLStehCT5mQ=";
	c:"Subject: Re: who will edit the draft ?";
	c:"From: Michael Thomas <mat@cisco.com>";
	c:"Date: Thu, 20 Jan 2005 14:22:00 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>



--=-LqEHyvl7gwvFgooJl54u
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Thu, 2005-01-20 at 13:48, Jan Vilhuber wrote:
> I guess saying "I haven't read 2401bis" won't be a good excuse for not
> implementing any features from it, is it?

Well it's probably better than implementing
features *without* reading it ;-)

		Mike

--=-LqEHyvl7gwvFgooJl54u
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iQCVAwUAQfAvCLMsDAj/Eq++AQIoggP+KMXuh3Gytvfy05ayBZUA2GZiw67TEzRS
nJOUDvfy2k0Y1tJ1MROjW7BX4VjGI3uS12dwvci61UKmsLaat1vwp7FP/e+2bWe+
bEeDipWvD0uNgobmNMpyoOBzf4580cCvfWioJQ4TTBiIQsm8+XsnwRjsp64/znZP
c5Cds2ng5KU=
=R95H
-----END PGP SIGNATURE-----

--=-LqEHyvl7gwvFgooJl54u--



From owner-ietf-kink@mail.vpnc.org  Thu Jan 20 20:00:18 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02889
	for <kink-archive@lists.ietf.org>; Thu, 20 Jan 2005 20:00:16 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0L0vu88011548;
	Thu, 20 Jan 2005 16:57:56 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0L0vuK1011547;
	Thu, 20 Jan 2005 16:57:56 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from nasten.nanohz.org (usen-220x218x5x242.ap-US00.usen.ad.jp [220.218.5.242])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0L0vtSr011147
	for <ietf-kink@vpnc.org>; Thu, 20 Jan 2005 16:57:55 -0800 (PST)
	(envelope-from kamada@nanohz.org)
Received: from nasten.nanohz.org (localhost [127.0.0.1])
	by nasten.nanohz.org (Postfix) with ESMTP id 8645D11
	for <ietf-kink@vpnc.org>; Fri, 21 Jan 2005 09:57:31 +0900 (JST)
Received: from mitana.nanohz.org ([2001:240:2:0:202:8aff:fefa:bec0])
	by nasten.nanohz.org (smtpsugar 1.1) with ESMTPA
	id 0yXqBG; Fri, 21 Jan 2005 09:57:31 +0900 (JST)
Date: Fri, 21 Jan 2005 09:58:20 +0900
Message-ID: <20050121095820RV%kamada@nanohz.org>
From: "KAMADA Ken'ichi" <kamada@nanohz.org>
To: ietf-kink@vpnc.org
Subject: Re: KINK issue list
In-Reply-To: <1106244665.2953.78.camel@thomasm-lnx.cisco.com>
References: <20050120102450Q.sakane@kame.net>
	<20050120103639RZ%kamada@nanohz.org>
	<20050120110448RR%kamada@nanohz.org>
	<1106244665.2953.78.camel@thomasm-lnx.cisco.com>
User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.3.50
 (i386-unknown-netbsdelf2.0G) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


At Thu, 20 Jan 2005 10:11:05 -0800,
Michael Thomas <mat@cisco.com> wrote:
> 
>                                              Maybe what
> we can do is keep a master list here, the proposed 
> resolution, or whether to close the issue due to it being
> not a problem.

Yes, I'll maintain this list.  I'll do that in e-mails for a
meanwhile, and if things become complicated I may prepare an
issue tracker.

-- 
KAMADA Ken'ichi <kamada@nanohz.org>



From owner-ietf-kink@mail.vpnc.org  Thu Jan 20 20:11:48 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03621
	for <kink-archive@lists.ietf.org>; Thu, 20 Jan 2005 20:11:47 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0L08SIq051349;
	Thu, 20 Jan 2005 16:08:28 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0L08SPd051348;
	Thu, 20 Jan 2005 16:08:28 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from march.taca.jp (vbox.nezu.wide.ad.jp [203.178.142.195])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0L08R4L051131
	for <ietf-kink@vpnc.org>; Thu, 20 Jan 2005 16:08:27 -0800 (PST)
	(envelope-from nov@tahi.org)
Received: from localhost (vbox.nezu.wide.ad.jp [203.178.142.195])
	by march.taca.jp (Postfix) with ESMTP
	id DA61E1FBC2; Fri, 21 Jan 2005 09:08:05 +0900 (JST)
Date: Fri, 21 Jan 2005 09:08:04 +0900 (JST)
Message-Id: <20050121.090804.81663863.nov@tahi.org>
To: hartmans-ietf@mit.edu
Cc: ietf-kink@vpnc.org
Subject: Re: AD review: draft-ietf-kink-kink [section 1-4]
From: Nobuo OKABE <nov@tahi.org>
In-Reply-To: <tslfz0wcbpv.fsf@cz.mit.edu>
References: <tslzmz65pzn.fsf@cz.mit.edu>
	<20050120.102207.68299999.nov@tahi.org>
	<tslfz0wcbpv.fsf@cz.mit.edu>
X-Mailer: Mew version 4.1 on Emacs 20.7 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


From: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: AD review: draft-ietf-kink-kink [section 1-4]
Date: Thu, 20 Jan 2005 11:22:04 -0500

> >>>>> "Nobuo" == Nobuo OKABE <nov@tahi.org> writes:
> 
>     Nobuo> It seems fair to me to postpone the date of fixing the
>     Nobuo> milestones from February 7 to after IETF62.  Because the
>     Nobuo> progress of 1401bis has impact against the KINK draft.
> 
> I'm uncomfortable with doing this.  I think that we can set deadlines
> now.  If we find interesting new facts we can change the deadlines.
> I'll listen to concerns from the chairs if they believe they will not
> be able to get milestones ready by February 7 and evaluate those
> concerns.

My concern has resolved by the new milestones
proposed by the chair (Jan 19, 2005).
So I don't object to what you are saying here.

----- nobuo



From owner-ietf-kink@mail.vpnc.org  Thu Jan 20 21:00:04 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06501
	for <kink-archive@lists.ietf.org>; Thu, 20 Jan 2005 21:00:03 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0L1rVk9068017;
	Thu, 20 Jan 2005 17:53:31 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0L1rVks068016;
	Thu, 20 Jan 2005 17:53:31 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from sj-iport-1.cisco.com (sj-iport-1-in.cisco.com [171.71.176.70])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0L1rVlt067979
	for <ietf-kink@vpnc.org>; Thu, 20 Jan 2005 17:53:31 -0800 (PST)
	(envelope-from mat@cisco.com)
Received: from sj-core-2.cisco.com (171.71.177.254)
  by sj-iport-1.cisco.com with ESMTP; 20 Jan 2005 18:00:24 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j0L1rLl2001646;
	Thu, 20 Jan 2005 17:53:21 -0800 (PST)
Received: from thomasm-lnx.cisco.com (thomasm-lnx.cisco.com [171.71.96.50])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j0L1npAJ006698;
	Thu, 20 Jan 2005 17:49:51 -0800
Subject: Re: KINK issue list
From: Michael Thomas <mat@cisco.com>
To: "KAMADA Ken'ichi" <kamada@nanohz.org>
Cc: ietf-kink@vpnc.org
In-Reply-To: <20050121095820RV%kamada@nanohz.org>
References: <20050120102450Q.sakane@kame.net>
	 <20050120103639RZ%kamada@nanohz.org> <20050120110448RR%kamada@nanohz.org>
	 <1106244665.2953.78.camel@thomasm-lnx.cisco.com>
	 <20050121095820RV%kamada@nanohz.org>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-gZkN8kHUSfMBldd7uhNG"
Organization: Cisco Systems
Message-Id: <1106272402.2953.86.camel@thomasm-lnx.cisco.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 
Date: Thu, 20 Jan 2005 17:53:22 -0800
IIM-SIG: v:"1.1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1106272191.244457"; x:"432200"; a:"rsa-sha1"; b:"nofws:924";
	e:"Iw=="; n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2p"
	"XIweAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRUtW+c43sl9jC"
	"50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"sAg6zkld4/u0IZtbXIy2KLez4An/JbN9Te7nvOxVGQJgfoJPYCgMOPnb2edldFOkYoHgGIVG"
	"cnqgzRBMfPezqApIY0gDEqv0aya4j1aPy7tehmN6Aglw6iG9jmGX2lH+wp90/5YQsDWSrozWwuG"
	"Q8917eHhDtq+gcZLByOrj4ss=";
	c:"Subject: Re: KINK issue list";
	c:"From: Michael Thomas <mat@cisco.com>";
	c:"Date: Thu, 20 Jan 2005 17:53:22 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>



--=-gZkN8kHUSfMBldd7uhNG
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable


On Thu, 2005-01-20 at 16:58, KAMADA Ken'ichi wrote:
> At Thu, 20 Jan 2005 10:11:05 -0800,
> Michael Thomas <mat@cisco.com> wrote:
> >=20
> >                                              Maybe what
> > we can do is keep a master list here, the proposed=20
> > resolution, or whether to close the issue due to it being
> > not a problem.
>=20
> Yes, I'll maintain this list.  I'll do that in e-mails for a
> meanwhile, and if things become complicated I may prepare an
> issue tracker.

Excellent, this will be a big help. I really
appreciate the help.

		Mike

--=-gZkN8kHUSfMBldd7uhNG
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iQCVAwUAQfBgkrMsDAj/Eq++AQIBOAQAi473a+ZP1igGgH4R9Ih8LXgZMEHvDVJf
p5Nu3dAu7MISkLBhRBxPGx55HCOx3SgEBG0AqtJa4/DUT8X16ZQOnggP9AVUXIWw
9Ovqpy+mhiNvBB5r6vtGGpuzgNwsTPtItlwOL4JJqLkNh5vGQA9HVkuEoJouvg0Z
i/nNSiKVxLc=
=7gzp
-----END PGP SIGNATURE-----

--=-gZkN8kHUSfMBldd7uhNG--



From owner-ietf-kink@mail.vpnc.org  Thu Jan 20 23:57:29 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16302
	for <kink-archive@lists.ietf.org>; Thu, 20 Jan 2005 23:57:29 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0L4qB5W082293;
	Thu, 20 Jan 2005 20:52:11 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0L4qB7H082292;
	Thu, 20 Jan 2005 20:52:11 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from miyazawa.org (usen-221x116x13x66.ap-US01.usen.ad.jp [221.116.13.66])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0L4qAmp082278
	for <ietf-kink@vpnc.org>; Thu, 20 Jan 2005 20:52:10 -0800 (PST)
	(envelope-from kazunori@miyazawa.org)
Received: from [IPv6:2001:240:2:0:1d77:4b64:9367:d0ec] ([2001:240:2:0:1d77:4b64:9367:d0ec])
  (AUTH: LOGIN kazunori, SSL: TLSv1/SSLv3,128bits,RC4-MD5)
  by miyazawa.org with esmtp; Fri, 21 Jan 2005 13:45:26 +0900
  id 000008FF.41F088E6.000011B0
Message-ID: <41F08A3F.4060103@miyazawa.org>
Date: Fri, 21 Jan 2005 13:51:11 +0900
From: Kazunori Miyazawa <kazunori@miyazawa.org>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
CC: ietf-kink@vpnc.org
Subject: Re: who will edit the draft ?
References: <20050120102450Q.sakane@kame.net>	<1106185907.2953.37.camel@thomasm-lnx.cisco.com> <tsld5vzc13n.fsf@cz.mit.edu>
In-Reply-To: <tsld5vzc13n.fsf@cz.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


Sam Hartman wrote:
>>>>>>"Michael" == Michael Thomas <mat@cisco.com> writes:
> 

<snip>

> * A presentation making sure we understand the difference between
>      2401bis conformance   and ikev2 conformance

Excuse me, I could not understand above sentence.

RFC2401bis specifies IP security archietecture.
However, IKEv2 is the key exchange protocol.

Does it mean whether any confilict between RFC2401bis and IKEv2 is
when we implement them?

--
Kazunori Miyazawa




From owner-ietf-kink@mail.vpnc.org  Sat Jan 22 10:21:43 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10106
	for <kink-archive@lists.ietf.org>; Sat, 22 Jan 2005 10:21:43 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0MFGnPn010593;
	Sat, 22 Jan 2005 07:16:49 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0MFGnST010592;
	Sat, 22 Jan 2005 07:16:49 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from cz.mit.edu (vomit-synonyms.naming-schemes.org [67.65.18.118])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0MFGm8Z010585
	for <ietf-kink@vpnc.org>; Sat, 22 Jan 2005 07:16:48 -0800 (PST)
	(envelope-from hartmans@mit.edu)
Received: by cz.mit.edu (Postfix, from userid 8042)
	id 7D9B0E0077; Fri, 21 Jan 2005 15:45:27 -0500 (EST)
To: Kazunori Miyazawa <kazunori@miyazawa.org>
Cc: ietf-kink@vpnc.org
Subject: Re: who will edit the draft ?
References: <20050120102450Q.sakane@kame.net>
	<1106185907.2953.37.camel@thomasm-lnx.cisco.com>
	<tsld5vzc13n.fsf@cz.mit.edu> <41F08A3F.4060103@miyazawa.org>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Fri, 21 Jan 2005 11:33:23 -0500
In-Reply-To: <41F08A3F.4060103@miyazawa.org> (Kazunori Miyazawa's message of
 "Fri, 21 Jan 2005 13:51:11 +0900")
Message-ID: <tslu0palp2k.fsf@cz.mit.edu>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


>>>>> "Kazunori" == Kazunori Miyazawa <kazunori@miyazawa.org> writes:

    Kazunori> RFC2401bis specifies IP security archietecture.
    Kazunori> However, IKEv2 is the key exchange protocol.

I think some people on this list have assumed that when I said we need
to comply with 2401bis that I invisioned changing our references to
ikev2 instead of ikev1.  These issues seem to be complicated because
2401bis mandates ikev2 although it still supports ikev1 as an option.

I want to make sure this distinction is untangled for the group.

--Sam



From owner-ietf-kink@mail.vpnc.org  Tue Jan 25 20:52:04 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06936
	for <kink-archive@lists.ietf.org>; Tue, 25 Jan 2005 20:52:01 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0Q1hOZs036087;
	Tue, 25 Jan 2005 17:43:24 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0Q1hOuP036086;
	Tue, 25 Jan 2005 17:43:24 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from march.taca.jp (vbox.nezu.wide.ad.jp [203.178.142.195])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0Q1hEVV036060
	for <ietf-kink@vpnc.org>; Tue, 25 Jan 2005 17:43:14 -0800 (PST)
	(envelope-from nov@tahi.org)
Received: from localhost (vbox.nezu.wide.ad.jp [203.178.142.195])
	by march.taca.jp (Postfix) with ESMTP
	id B7D621FBC2; Wed, 26 Jan 2005 10:42:54 +0900 (JST)
Date: Wed, 26 Jan 2005 10:42:54 +0900 (JST)
Message-Id: <20050126.104254.59908100.nov@tahi.org>
To: derek@ihtfp.com
Cc: mat@cisco.com, sakane@kame.net, ietf-kink@vpnc.org
Subject: Re: who will edit the draft ?
From: Nobuo OKABE <nov@tahi.org>
In-Reply-To: <sjm651syi02.fsf@dogbert.ihtfp.org>
References: <20050120102450Q.sakane@kame.net>
	<1106185907.2953.37.camel@thomasm-lnx.cisco.com>
	<sjm651syi02.fsf@dogbert.ihtfp.org>
X-Mailer: Mew version 4.1 on Emacs 20.7 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


Dear Chairs,

From: Derek Atkins <derek@ihtfp.com>
Subject: Re: who will edit the draft ?
Date: Wed, 19 Jan 2005 21:03:09 -0500

> > Has a decision been made on wg meeting in MPLS?
> > I'm hoping that the issues don't require a f2f 
> > meeting, but it would be good to know one way or
> > the other.
> 
> I'm willing to go either way.  If the WG believes we need a face to
> face meeting then I'll gladly arrange for one.

Yes please.

I also think that WG needs a meeting.
The agenda which Sam has proposed is good for the start.
It will be fixed through discussion on the ML.

I would be happy if the meeting is not held Friday
when I will go back to Japan because of my business reasons.
However, I can re-arrange my travel schedule at this moment
if necessary.
So please let me know the (possible) day of the meeting.

Thank you for your help

----- nobuo



From owner-ietf-kink@mail.vpnc.org  Tue Jan 25 21:30:50 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10252
	for <kink-archive@lists.ietf.org>; Tue, 25 Jan 2005 21:30:50 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0Q2P9YL039695;
	Tue, 25 Jan 2005 18:25:10 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0Q2P9ab039683;
	Tue, 25 Jan 2005 18:25:09 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from march.taca.jp (vbox.nezu.wide.ad.jp [203.178.142.195])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0Q2OXWU039600
	for <ietf-kink@vpnc.org>; Tue, 25 Jan 2005 18:25:00 -0800 (PST)
	(envelope-from nov@tahi.org)
Received: from localhost (vbox.nezu.wide.ad.jp [203.178.142.195])
	by march.taca.jp (Postfix) with ESMTP
	id 620F71FBC2; Wed, 26 Jan 2005 11:24:33 +0900 (JST)
Date: Wed, 26 Jan 2005 11:24:33 +0900 (JST)
Message-Id: <20050126.112433.102614487.nov@tahi.org>
To: derek@ihtfp.com
Cc: sakane@kame.net, ietf-kink@vpnc.org
Subject: Re: who will edit the draft ?
From: Nobuo OKABE <nov@tahi.org>
In-Reply-To: <sjmis5syiu9.fsf@dogbert.ihtfp.org>
References: <20050120102450Q.sakane@kame.net>
	<sjmis5syiu9.fsf@dogbert.ihtfp.org>
X-Mailer: Mew version 4.1 on Emacs 20.7 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


From: Derek Atkins <derek@ihtfp.com>
Subject: Re: who will edit the draft ?
Date: Wed, 19 Jan 2005 20:45:02 -0500

> Based on the existing set of issues I do not believe that your
> suggestions are reasonable -- they are way too aggresive.  I really do
> not believe that we'll reach consensus by April.  I think we have way
> too many issues.  Perhaps a better proposal for milestones are:
> 
> Mar 05	Review issues with kink-06
> Mar 05	Submit kink-07
> Jun 05	Reach consensus on necessary changes
> Jul 05	Submit kink-08
> Aug 05	WGLC
> Sep 05	Submit draft to IESG
> Jan 06	Begin Interop bakeoffs
> Feb 06	Document interop results.
> 
> Even this schedule is extremely agrressive, but IMHO actually
> achievable.  I don't think we can get concensus on all the open issues
> and make it past the IESG before Paris.

I think that the milestones are reasonable to recover the stall
even though it is very aggressive.
From implementor's viewpoint, we would like to fix the spec ASAP.

Please clear the meaning of "Mar 05 Review issues with kink-06".
I'm not sure, but we will not be able to reflect any effort
if review starts from March.

The most difficult part would be "Mar 05 Submit kink-07".
What should be the goal of draft-07?
The contents of the draft-07 can be a halfway
if we can not solve almost issues.
# and we don't have enough time to March.

thanks,

----- nobuo



From owner-ietf-kink@mail.vpnc.org  Tue Jan 25 22:52:45 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15087
	for <kink-archive@lists.ietf.org>; Tue, 25 Jan 2005 22:52:45 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0Q3nGPV045784;
	Tue, 25 Jan 2005 19:49:16 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0Q3nGhh045783;
	Tue, 25 Jan 2005 19:49:16 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from biscayne-one-station.mit.edu (BISCAYNE-ONE-STATION.MIT.EDU [18.7.7.80])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0Q3nFFJ045775
	for <ietf-kink@vpnc.org>; Tue, 25 Jan 2005 19:49:15 -0800 (PST)
	(envelope-from raeburn@MIT.EDU)
Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103])
	by biscayne-one-station.mit.edu (8.12.4/8.9.2) with ESMTP id j0Q3nDEm012730
	for <ietf-kink@vpnc.org>; Tue, 25 Jan 2005 22:49:13 -0500 (EST)
Received: from [18.101.0.226] ([18.101.0.226])
	(authenticated bits=0)
        (User authenticated as raeburn@ATHENA.MIT.EDU)
	by outgoing.mit.edu (8.12.4/8.12.4) with ESMTP id j0Q3nBsR014336
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT)
	for <ietf-kink@vpnc.org>; Tue, 25 Jan 2005 22:49:12 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v619.2)
In-Reply-To: <20050126.104254.59908100.nov@tahi.org>
References: <20050120102450Q.sakane@kame.net> <1106185907.2953.37.camel@thomasm-lnx.cisco.com> <sjm651syi02.fsf@dogbert.ihtfp.org> <20050126.104254.59908100.nov@tahi.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <d75da23eeb74a40f7403469e3b58c141@mit.edu>
Content-Transfer-Encoding: 7bit
From: Ken Raeburn <raeburn@MIT.EDU>
Subject: Re: who will edit the draft ?
Date: Tue, 25 Jan 2005 22:49:09 -0500
To: ietf-kink@vpnc.org
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: -4.9
X-Spam-Flag: NO
X-Scanned-By: MIMEDefang 2.42
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


On Jan 25, 2005, at 20:42, Nobuo OKABE wrote:
> I also think that WG needs a meeting.
> The agenda which Sam has proposed is good for the start.
> It will be fixed through discussion on the ML.
>
> I would be happy if the meeting is not held Friday
> when I will go back to Japan because of my business reasons.
> However, I can re-arrange my travel schedule at this moment
> if necessary.
> So please let me know the (possible) day of the meeting.

The schedule typically isn't set until shortly before the conference, 
and in fact is still subject to change even then.

Ken



From owner-ietf-kink@mail.vpnc.org  Tue Jan 25 23:05:27 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15792
	for <kink-archive@lists.ietf.org>; Tue, 25 Jan 2005 23:05:27 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0Q415W9046995;
	Tue, 25 Jan 2005 20:01:05 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0Q414Vk046993;
	Tue, 25 Jan 2005 20:01:04 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from march.taca.jp (vbox.nezu.wide.ad.jp [203.178.142.195])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0Q40xTZ046960
	for <ietf-kink@vpnc.org>; Tue, 25 Jan 2005 20:00:59 -0800 (PST)
	(envelope-from nov@tahi.org)
Received: from localhost (vbox.nezu.wide.ad.jp [203.178.142.195])
	by march.taca.jp (Postfix) with ESMTP id 4B80F1FBC2
	for <ietf-kink@vpnc.org>; Wed, 26 Jan 2005 13:00:58 +0900 (JST)
Date: Wed, 26 Jan 2005 13:00:57 +0900 (JST)
Message-Id: <20050126.130057.85807426.nov@tahi.org>
To: ietf-kink@vpnc.org
Subject: Re: who will edit the draft ?
From: Nobuo OKABE <nov@tahi.org>
In-Reply-To: <d75da23eeb74a40f7403469e3b58c141@mit.edu>
References: <sjm651syi02.fsf@dogbert.ihtfp.org>
	<20050126.104254.59908100.nov@tahi.org>
	<d75da23eeb74a40f7403469e3b58c141@mit.edu>
X-Mailer: Mew version 4.1 on Emacs 20.7 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


From: Ken Raeburn <raeburn@MIT.EDU>
Subject: Re: who will edit the draft ?
Date: Tue, 25 Jan 2005 22:49:09 -0500

> 
> On Jan 25, 2005, at 20:42, Nobuo OKABE wrote:
> > I also think that WG needs a meeting.
> > The agenda which Sam has proposed is good for the start.
> > It will be fixed through discussion on the ML.
> >
> > I would be happy if the meeting is not held Friday
> > when I will go back to Japan because of my business reasons.
> > However, I can re-arrange my travel schedule at this moment
> > if necessary.
> > So please let me know the (possible) day of the meeting.
> 
> The schedule typically isn't set until shortly before the conference, 
> and in fact is still subject to change even then.

OK. I'll try to re-arrange my travel schedule.
Thank you for your advice.

----- nobuo



From owner-ietf-kink@mail.vpnc.org  Tue Jan 25 23:23:48 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17180
	for <kink-archive@lists.ietf.org>; Tue, 25 Jan 2005 23:23:47 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0Q4KVNB048771;
	Tue, 25 Jan 2005 20:20:32 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0Q4KU4O048770;
	Tue, 25 Jan 2005 20:20:31 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from dogbert.ihtfp.org (me@[204.107.200.33])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0Q4K73Z048698
	for <ietf-kink@vpnc.org>; Tue, 25 Jan 2005 20:20:13 -0800 (PST)
	(envelope-from warlord@MIT.EDU)
Received: (from warlord@localhost) by dogbert.ihtfp.org (8.12.9)
	id j0Q4IOfJ000425; Tue, 25 Jan 2005 23:18:24 -0500
From: Derek Atkins <derek@ihtfp.com>
To: Nobuo OKABE <nov@tahi.org>
Cc: sakane@kame.net, ietf-kink@vpnc.org
Subject: Re: who will edit the draft ?
References: <20050120102450Q.sakane@kame.net>
	<sjmis5syiu9.fsf@dogbert.ihtfp.org>
	<20050126.112433.102614487.nov@tahi.org>
Date: Tue, 25 Jan 2005 23:18:24 -0500
In-Reply-To: <20050126.112433.102614487.nov@tahi.org> (Nobuo OKABE's message
	of "Wed, 26 Jan 2005 11:24:33 +0900 (JST)")
Message-ID: <sjm3bwokelr.fsf@dogbert.ihtfp.org>
User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


Nobuo OKABE <nov@tahi.org> writes:

> Please clear the meaning of "Mar 05 Review issues with kink-06".
> I'm not sure, but we will not be able to reflect any effort
> if review starts from March.

Milestones are completion dates, not commencement dates.  This means
that by March, 2005 we should have completed review of the issues with
kink-06.

> The most difficult part would be "Mar 05 Submit kink-07".
> What should be the goal of draft-07?

draft 07 should have the changes that reflect the concensus of changes
based on the issues of draft-06.

> The contents of the draft-07 can be a halfway
> if we can not solve almost issues.
> # and we don't have enough time to March.

Drafts are easy.  If it were me I'd say we should have a new draft
every 2-4 weeks.  But I'm not the editor.  Please don't get caught up
in draft numbers.

-derek

-- 
       Derek Atkins                 617-623-3745
       derek@ihtfp.com             www.ihtfp.com
       Computer and Internet Security Consultant



From owner-ietf-kink@mail.vpnc.org  Tue Jan 25 23:23:59 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17200
	for <kink-archive@lists.ietf.org>; Tue, 25 Jan 2005 23:23:59 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0Q4LOYb048899;
	Tue, 25 Jan 2005 20:21:24 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0Q4LOXQ048898;
	Tue, 25 Jan 2005 20:21:24 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from dogbert.ihtfp.org (me@DOGBERT.IHTFP.ORG [204.107.200.33])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0Q4LNGt048892
	for <ietf-kink@vpnc.org>; Tue, 25 Jan 2005 20:21:24 -0800 (PST)
	(envelope-from warlord@MIT.EDU)
Received: (from warlord@localhost) by dogbert.ihtfp.org (8.12.9)
	id j0Q4JbZ1000434; Tue, 25 Jan 2005 23:19:37 -0500
From: Derek Atkins <derek@ihtfp.com>
To: Nobuo OKABE <nov@tahi.org>
Cc: mat@cisco.com, sakane@kame.net, ietf-kink@vpnc.org
Subject: Agenda items (was: Re: who will edit the draft ?)
References: <20050120102450Q.sakane@kame.net>
	<1106185907.2953.37.camel@thomasm-lnx.cisco.com>
	<sjm651syi02.fsf@dogbert.ihtfp.org>
	<20050126.104254.59908100.nov@tahi.org>
Date: Tue, 25 Jan 2005 23:19:37 -0500
In-Reply-To: <20050126.104254.59908100.nov@tahi.org> (Nobuo OKABE's message of
	"Wed, 26 Jan 2005 10:42:54 +0900 (JST)")
Message-ID: <sjmy8egizza.fsf_-_@dogbert.ihtfp.org>
User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


Nobuo OKABE <nov@tahi.org> writes:

> I also think that WG needs a meeting.

An agenda slot has been requested for IETF-62.  If you have a
presentation you'd like to make I humbly request agenda items for the
meeting.

Thanks,

-derek

-- 
       Derek Atkins                 617-623-3745
       derek@ihtfp.com             www.ihtfp.com
       Computer and Internet Security Consultant



From owner-ietf-kink@mail.vpnc.org  Tue Jan 25 23:42:39 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA18102
	for <kink-archive@lists.ietf.org>; Tue, 25 Jan 2005 23:42:39 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0Q4epi0049900;
	Tue, 25 Jan 2005 20:40:51 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0Q4ep8n049899;
	Tue, 25 Jan 2005 20:40:51 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from march.taca.jp (vbox.nezu.wide.ad.jp [203.178.142.195])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0Q4ejgx049891
	for <ietf-kink@vpnc.org>; Tue, 25 Jan 2005 20:40:46 -0800 (PST)
	(envelope-from nov@tahi.org)
Received: from localhost (vbox.nezu.wide.ad.jp [203.178.142.195])
	by march.taca.jp (Postfix) with ESMTP
	id 71C961FBC4; Wed, 26 Jan 2005 13:40:45 +0900 (JST)
Date: Wed, 26 Jan 2005 13:40:45 +0900 (JST)
Message-Id: <20050126.134045.34663171.nov@tahi.org>
To: derek@ihtfp.com
Cc: mat@cisco.com, sakane@kame.net, ietf-kink@vpnc.org
Subject: Re: Agenda items
From: Nobuo OKABE <nov@tahi.org>
In-Reply-To: <sjmy8egizza.fsf_-_@dogbert.ihtfp.org>
References: <sjm651syi02.fsf@dogbert.ihtfp.org>
	<20050126.104254.59908100.nov@tahi.org>
	<sjmy8egizza.fsf_-_@dogbert.ihtfp.org>
X-Mailer: Mew version 4.1 on Emacs 20.7 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


From: Derek Atkins <derek@ihtfp.com>
Subject: Agenda items (was: Re: who will edit the draft ?)
Date: Tue, 25 Jan 2005 23:19:37 -0500

> > I also think that WG needs a meeting.
> 
> An agenda slot has been requested for IETF-62.  If you have a
> presentation you'd like to make I humbly request agenda items for the
> meeting.

We are considering one (or more?) of agenda items,
and will let you know when taking shape.

thanks,

----- nobuo



From owner-ietf-kink@mail.vpnc.org  Thu Jan 27 00:40:23 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA04128
	for <kink-archive@lists.ietf.org>; Thu, 27 Jan 2005 00:40:20 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0R5ZBgt099671;
	Wed, 26 Jan 2005 21:35:11 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0R5ZB9n099670;
	Wed, 26 Jan 2005 21:35:11 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from papa.tanu.org (kame195.kame.net [203.178.141.195])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0R5Z6De099643
	for <ietf-kink@vpnc.org>; Wed, 26 Jan 2005 21:35:10 -0800 (PST)
	(envelope-from sakane@kame.net)
Received: from localhost (cp.64translator.com [202.214.123.2])
	by papa.tanu.org (8.12.9/8.12.8) with ESMTP id j0R5Z2hB075057
	for <ietf-kink@vpnc.org>; Thu, 27 Jan 2005 14:35:02 +0900 (JST)
	(envelope-from sakane@kame.net)
To: ietf-kink@vpnc.org
Subject: Re: KINK should referenece to IKEv2?
In-Reply-To: Your message of "Thu, 20 Jan 2005 14:57:49 -0500"
	<tslllanc1qa.fsf@cz.mit.edu>
References: <tslllanc1qa.fsf@cz.mit.edu>
X-Mailer: Cue version 0.8 (041108-2350/sakane)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Message-Id: <20050127143507Z.sakane@kame.net>
Date: Thu, 27 Jan 2005 14:35:07 +0900
From: Shoichi Sakane <sakane@kame.net>
X-Dispatcher: imput version 20030322(IM144)
Lines: 15
X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c
	on papa.tanu.org
X-Virus-Status: Clean
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


> Speaking as an AD, if 2401bis is approved by IETF 62, Kink will be
> based on 2401bis.  If not, then it depends on where 2401bis is, where
> Kink is, and how fast things are moving.

I dont understand why KINK will be based on 2401bis when 2401bis
is approved by IETF62.  There are lots of platforms based on 2401.
KINK should be based on 2401 in order to deploy it.  If the market
will not choice 2401bis and if a kink implementation based on 2401bis
does not work on a platform based on 2401, then KINK will not deploy.

it is not easy to know how difference between 2401bis and 2401,
and it is not easy to know if a key management daemon based on
2401bis will work on a platform based on 2401.  so I said in previous
mail that we should make kink based on 2401 then make kink based on
2401bis.  kink header has a version field.



From owner-ietf-kink@mail.vpnc.org  Thu Jan 27 03:17:01 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00532
	for <kink-archive@lists.ietf.org>; Thu, 27 Jan 2005 03:17:00 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0R8DpGj067056;
	Thu, 27 Jan 2005 00:13:51 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0R8DpJ8067055;
	Thu, 27 Jan 2005 00:13:51 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from nasten.nanohz.org (usen-220x218x5x242.ap-US00.usen.ad.jp [220.218.5.242])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0R8Dpoa066898
	for <ietf-kink@vpnc.org>; Thu, 27 Jan 2005 00:13:51 -0800 (PST)
	(envelope-from kamada@nanohz.org)
Received: from nasten.nanohz.org (localhost [127.0.0.1])
	by nasten.nanohz.org (Postfix) with ESMTP id E43F711
	for <ietf-kink@vpnc.org>; Thu, 27 Jan 2005 17:13:41 +0900 (JST)
Received: from mitana.nanohz.org ([2001:240:2:0:202:8aff:fefa:bec0])
	by nasten.nanohz.org (smtpsugar 1.1) with ESMTPA
	id 3aJqzJ; Thu, 27 Jan 2005 17:13:41 +0900 (JST)
Date: Thu, 27 Jan 2005 17:14:41 +0900
Message-ID: <20050127171441FF%kamada@nanohz.org>
From: "KAMADA Ken'ichi" <kamada@nanohz.org>
To: ietf-kink@vpnc.org
Subject: Responder's nonce when 3-way (Re: KINK issue list)
In-Reply-To: <20050120110448RR%kamada@nanohz.org>
References: <20050120102450Q.sakane@kame.net>
	<20050120103639RZ%kamada@nanohz.org>
	<20050120110448RR%kamada@nanohz.org>
User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.3.50
 (i386-unknown-netbsdelf2.0G) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


At Thu, 20 Jan 2005 11:04:48 +0900,
"KAMADA Ken'ichi" <kamada@nanohz.org> wrote:
> 
> [*] When 3-way, is responder's nonce MUST or SHOULD? (section 4.3 and 7.3)
> 
> 	Sec 4.3 and 7.3 use SHOULD and MUST respectively regarding when the 
> 	nonce should be used.  If the circumstances they're describing are 
> 	different, that's okay, but if so, I missed it on first reading.
> 	(Ken Raeburn)

They are talking the same situation and the requirement levels should
be aligned.  I think SHOULD is appropriate because non-returning
responder's nonce does not break interoperabilities.

-- 
KAMADA Ken'ichi <kamada@nanohz.org>



From owner-ietf-kink@mail.vpnc.org  Thu Jan 27 03:17:11 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00555
	for <kink-archive@lists.ietf.org>; Thu, 27 Jan 2005 03:17:11 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0R8Flcv068816;
	Thu, 27 Jan 2005 00:15:47 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0R8Flql068812;
	Thu, 27 Jan 2005 00:15:47 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from nasten.nanohz.org (usen-220x218x5x242.ap-US00.usen.ad.jp [220.218.5.242])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0R8Fkgq068794
	for <ietf-kink@vpnc.org>; Thu, 27 Jan 2005 00:15:46 -0800 (PST)
	(envelope-from kamada@nanohz.org)
Received: from nasten.nanohz.org (localhost [127.0.0.1])
	by nasten.nanohz.org (Postfix) with ESMTP id 2C30811
	for <ietf-kink@vpnc.org>; Thu, 27 Jan 2005 17:15:46 +0900 (JST)
Received: from mitana.nanohz.org ([2001:240:2:0:202:8aff:fefa:bec0])
	by nasten.nanohz.org (smtpsugar 1.1) with ESMTPA
	id 1pagmQ; Thu, 27 Jan 2005 17:15:46 +0900 (JST)
Date: Thu, 27 Jan 2005 17:16:45 +0900
Message-ID: <20050127171645FM%kamada@nanohz.org>
From: "KAMADA Ken'ichi" <kamada@nanohz.org>
To: ietf-kink@vpnc.org
Subject: Checksum (Re: KINK issue list)
In-Reply-To: <20050120110448RR%kamada@nanohz.org>
References: <20050120102450Q.sakane@kame.net>
	<20050120103639RZ%kamada@nanohz.org>
	<20050120110448RR%kamada@nanohz.org>
User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.3.50
 (i386-unknown-netbsdelf2.0G) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


At Thu, 20 Jan 2005 11:04:48 +0900,
"KAMADA Ken'ichi" <kamada@nanohz.org> wrote:
> 
> [**] etype does not directly indicate checksum type (section 5)
> 
> 	a key's encryption type does not directly indicate 
> 	a checksum type, it indicates an encryption(-with-integrity-protection) 
> 	scheme, which does include a required-to-implement checksum type
> 	(Ken Raeburn)
> 
> [**] Kerberos allows variable length checksum (section 5)
> 
> 	I'd have to go back and check, but I don't think we require that 
> 	a given checksum type have a fixed output size, so "leave X amount of 
> 	space and fill it with zero for computing the checksum" is questionable 
> 	too.  (Ken Raeburn)
> 
> [*] Kerberos checksum is not deterministic (section 5)

With regard to these three issues, I'd propose using HMAC as a KINK
checksum.
According to kcrypto, each etype based on simplified profile and
etype based on 3DES has a HMAC as its attribute.  Let's use it as is.
DES-based etypes (des-cbc-md5, des-cbc-md4, and des-cbc-crc) have
no HMAC associated with them, so use HMAC-MD5.

My main concern with this proposal is whether all future etypes
will be based on simplified profile (have HMAC, I mean) or not.

-- 
KAMADA Ken'ichi <kamada@nanohz.org>



From owner-ietf-kink@mail.vpnc.org  Thu Jan 27 03:20:24 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00763
	for <kink-archive@lists.ietf.org>; Thu, 27 Jan 2005 03:20:23 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0R8G5XK069109;
	Thu, 27 Jan 2005 00:16:05 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0R8G5nd069108;
	Thu, 27 Jan 2005 00:16:05 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from nasten.nanohz.org (usen-220x218x5x242.ap-US00.usen.ad.jp [220.218.5.242])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0R8G4ns069090
	for <ietf-kink@vpnc.org>; Thu, 27 Jan 2005 00:16:05 -0800 (PST)
	(envelope-from kamada@nanohz.org)
Received: from nasten.nanohz.org (localhost [127.0.0.1])
	by nasten.nanohz.org (Postfix) with ESMTP id 37DE21B
	for <ietf-kink@vpnc.org>; Thu, 27 Jan 2005 17:16:04 +0900 (JST)
Received: from mitana.nanohz.org ([2001:240:2:0:202:8aff:fefa:bec0])
	by nasten.nanohz.org (smtpsugar 1.1) with ESMTPA
	id 0DtEw1; Thu, 27 Jan 2005 17:16:04 +0900 (JST)
Date: Thu, 27 Jan 2005 17:17:03 +0900
Message-ID: <20050127171703FZ%kamada@nanohz.org>
From: "KAMADA Ken'ichi" <kamada@nanohz.org>
To: ietf-kink@vpnc.org
Subject: Subsession keys (Re: KINK issue list)
In-Reply-To: <20050120110448RR%kamada@nanohz.org>
References: <20050120102450Q.sakane@kame.net>
	<20050120103639RZ%kamada@nanohz.org>
	<20050120110448RR%kamada@nanohz.org>
User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.3.50
 (i386-unknown-netbsdelf2.0G) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


At Thu, 20 Jan 2005 11:04:48 +0900,
"KAMADA Ken'ichi" <kamada@nanohz.org> wrote:
> 
> [*] Subsession keys (section 5 and 8)
> 
> 	Are subsession keys ignored?  (Ken Raeburn)

I think they should not be ignored.

-- 
KAMADA Ken'ichi <kamada@nanohz.org>



From owner-ietf-kink@mail.vpnc.org  Thu Jan 27 10:37:48 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19574
	for <kink-archive@lists.ietf.org>; Thu, 27 Jan 2005 10:37:46 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0RFY9EN027388;
	Thu, 27 Jan 2005 07:34:09 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0RFY9k6027387;
	Thu, 27 Jan 2005 07:34:09 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from biscayne-one-station.mit.edu (BISCAYNE-ONE-STATION.MIT.EDU [18.7.7.80])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0RFY7cW027377
	for <ietf-kink@vpnc.org>; Thu, 27 Jan 2005 07:34:08 -0800 (PST)
	(envelope-from raeburn@MIT.EDU)
Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103])
	by biscayne-one-station.mit.edu (8.12.4/8.9.2) with ESMTP id j0RFY6rv021849;
	Thu, 27 Jan 2005 10:34:06 -0500 (EST)
Received: from [18.101.0.226] ([18.101.0.226])
	(authenticated bits=0)
        (User authenticated as raeburn@ATHENA.MIT.EDU)
	by outgoing.mit.edu (8.12.4/8.12.4) with ESMTP id j0RFY3W5028985
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT);
	Thu, 27 Jan 2005 10:34:04 -0500 (EST)
In-Reply-To: <20050127171645FM%kamada@nanohz.org>
References: <20050120102450Q.sakane@kame.net> <20050120103639RZ%kamada@nanohz.org> <20050120110448RR%kamada@nanohz.org> <20050127171645FM%kamada@nanohz.org>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <71f7d1221376acbc8485b84b11f8aaf4@mit.edu>
Content-Transfer-Encoding: 7bit
From: Ken Raeburn <raeburn@MIT.EDU>
Subject: Re: Checksum (Re: KINK issue list)
Date: Thu, 27 Jan 2005 10:34:03 -0500
To: ietf-kink@vpnc.org
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: -4.9
X-Spam-Flag: NO
X-Scanned-By: MIMEDefang 2.42
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


On Jan 27, 2005, at 03:16, KAMADA Ken'ichi wrote:
> With regard to these three issues, I'd propose using HMAC as a KINK
> checksum.
> According to kcrypto, each etype based on simplified profile and
> etype based on 3DES has a HMAC as its attribute.  Let's use it as is.
> DES-based etypes (des-cbc-md5, des-cbc-md4, and des-cbc-crc) have
> no HMAC associated with them, so use HMAC-MD5.
>
> My main concern with this proposal is whether all future etypes
> will be based on simplified profile (have HMAC, I mean) or not.

I think it's safe to say that eventually we will see new encryption 
types that do not use the simplified profile.  We may also see some 
that do, of course.  But with the variety of authenticated-encryption 
modes being produced and analyzed, it would make sense for us to stop 
constructing our own.  So I'd expect some future cryptosystem to be 
based on EAX, CCM, or some other such mode.

In order for KINK to not require updates for these future 
cryptosystems, you'd need to be able to say now how to determine what 
kind of checksum is to be used.

The only tricky issue in dealing with the required-to-implement 
checksum type should be the lack of a fixed size output.  Is it that 
hard to work around?  (Maybe omit the checksum field when computing the 
checksum?)

Ken



From owner-ietf-kink@mail.vpnc.org  Thu Jan 27 19:23:32 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15163
	for <kink-archive@lists.ietf.org>; Thu, 27 Jan 2005 19:23:30 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0S0FZEL069913;
	Thu, 27 Jan 2005 16:15:43 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0S0FIgj069894;
	Thu, 27 Jan 2005 16:15:18 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from nasten.nanohz.org (usen-220x218x5x242.ap-US00.usen.ad.jp [220.218.5.242])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0S0F0DO069864
	for <ietf-kink@vpnc.org>; Thu, 27 Jan 2005 16:15:11 -0800 (PST)
	(envelope-from kamada@nanohz.org)
Received: from nasten.nanohz.org (localhost [127.0.0.1])
	by nasten.nanohz.org (Postfix) with ESMTP id B0A665
	for <ietf-kink@vpnc.org>; Fri, 28 Jan 2005 09:14:57 +0900 (JST)
Received: from mitana.nanohz.org ([2001:240:2:0:202:8aff:fefa:bec0])
	by nasten.nanohz.org (smtpsugar 1.1) with ESMTPA
	id 2ltRVB; Fri, 28 Jan 2005 09:14:57 +0900 (JST)
Date: Fri, 28 Jan 2005 09:15:57 +0900
Message-ID: <20050128091557FT%kamada@nanohz.org>
From: "KAMADA Ken'ichi" <kamada@nanohz.org>
To: ietf-kink@vpnc.org
Subject: Re: Checksum
In-Reply-To: <20050128.090733.10900832.nov@tahi.org>
References: <20050120103639RZ%kamada@nanohz.org>
	<20050120110448RR%kamada@nanohz.org>
	<20050127171645FM%kamada@nanohz.org>
	<20050128.090733.10900832.nov@tahi.org>
User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.3.50
 (i386-unknown-netbsdelf2.0G) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


At Fri, 28 Jan 2005 09:07:33 +0900 (JST),
Nobuo OKABE <nov@tahi.org> wrote:
> 
> However, could you please assign serial number or something identity
> to every issue? It helps discussions.

I get it and will do.  Thanks

-- 
KAMADA Ken'ichi <kamada@nanohz.org>



From owner-ietf-kink@mail.vpnc.org  Thu Jan 27 20:11:00 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18832
	for <kink-archive@lists.ietf.org>; Thu, 27 Jan 2005 20:10:59 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0S080pL069406;
	Thu, 27 Jan 2005 16:08:00 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0S080Rx069405;
	Thu, 27 Jan 2005 16:08:00 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from march.taca.jp (vbox.nezu.wide.ad.jp [203.178.142.195])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0S07xac069364
	for <ietf-kink@vpnc.org>; Thu, 27 Jan 2005 16:07:59 -0800 (PST)
	(envelope-from nov@tahi.org)
Received: from localhost (vbox.nezu.wide.ad.jp [203.178.142.195])
	by march.taca.jp (Postfix) with ESMTP
	id BA56F1FBC2; Fri, 28 Jan 2005 09:07:42 +0900 (JST)
Date: Fri, 28 Jan 2005 09:07:33 +0900 (JST)
Message-Id: <20050128.090733.10900832.nov@tahi.org>
To: kamada@nanohz.org
Cc: ietf-kink@vpnc.org
Subject: Re: Checksum
From: Nobuo OKABE <nov@tahi.org>
In-Reply-To: <20050127171645FM%kamada@nanohz.org>
References: <20050120103639RZ%kamada@nanohz.org>
	<20050120110448RR%kamada@nanohz.org>
	<20050127171645FM%kamada@nanohz.org>
X-Mailer: Mew version 4.1 on Emacs 20.7 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


kamada-san,

Sorry, this is not a comment for your mail.
However, could you please assign serial number or something identity
to every issue? It helps discussions.

From: "KAMADA Ken'ichi" <kamada@nanohz.org>
Subject: Checksum (Re: KINK issue list)
Date: Thu, 27 Jan 2005 17:16:45 +0900

> 
> At Thu, 20 Jan 2005 11:04:48 +0900,
> "KAMADA Ken'ichi" <kamada@nanohz.org> wrote:
> > 
> > [**] etype does not directly indicate checksum type (section 5)
> > 
> > 	a key's encryption type does not directly indicate 
> > 	a checksum type, it indicates an encryption(-with-integrity-protection) 
> > 	scheme, which does include a required-to-implement checksum type
> > 	(Ken Raeburn)
> > 
> > [**] Kerberos allows variable length checksum (section 5)
> > 
> > 	I'd have to go back and check, but I don't think we require that 
> > 	a given checksum type have a fixed output size, so "leave X amount of 
> > 	space and fill it with zero for computing the checksum" is questionable 
> > 	too.  (Ken Raeburn)
> > 
> > [*] Kerberos checksum is not deterministic (section 5)
> 
> With regard to these three issues, I'd propose using HMAC as a KINK
> checksum.
> According to kcrypto, each etype based on simplified profile and
> etype based on 3DES has a HMAC as its attribute.  Let's use it as is.
> DES-based etypes (des-cbc-md5, des-cbc-md4, and des-cbc-crc) have
> no HMAC associated with them, so use HMAC-MD5.
> 
> My main concern with this proposal is whether all future etypes
> will be based on simplified profile (have HMAC, I mean) or not.

----- nobuo



From owner-ietf-kink@mail.vpnc.org  Thu Jan 27 20:51:29 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22302
	for <kink-archive@lists.ietf.org>; Thu, 27 Jan 2005 20:51:28 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0S1m6DH077534;
	Thu, 27 Jan 2005 17:48:06 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0S1m67I077533;
	Thu, 27 Jan 2005 17:48:06 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from biscayne-one-station.mit.edu (BISCAYNE-ONE-STATION.MIT.EDU [18.7.7.80])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0S1m5lX077527
	for <ietf-kink@vpnc.org>; Thu, 27 Jan 2005 17:48:05 -0800 (PST)
	(envelope-from raeburn@MIT.EDU)
Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103])
	by biscayne-one-station.mit.edu (8.12.4/8.9.2) with ESMTP id j0S1m1eY005572;
	Thu, 27 Jan 2005 20:48:01 -0500 (EST)
Received: from [18.18.1.76] (KEN-WIRELESS.MIT.EDU [18.18.1.76])
	(authenticated bits=0)
        (User authenticated as raeburn@ATHENA.MIT.EDU)
	by outgoing.mit.edu (8.12.4/8.12.4) with ESMTP id j0S1lv0a011752
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT);
	Thu, 27 Jan 2005 20:47:58 -0500 (EST)
In-Reply-To: <20050128090716FA%kamada@nanohz.org>
References: <20050120102450Q.sakane@kame.net> <20050120103639RZ%kamada@nanohz.org> <20050120110448RR%kamada@nanohz.org> <20050127171645FM%kamada@nanohz.org> <71f7d1221376acbc8485b84b11f8aaf4@mit.edu> <20050128090716FA%kamada@nanohz.org>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <4862abd2ff60e5469610a75831516214@mit.edu>
Content-Transfer-Encoding: 7bit
Cc: ietf-kink@vpnc.org
From: Ken Raeburn <raeburn@MIT.EDU>
Subject: Re: Checksum (Re: KINK issue list)
Date: Thu, 27 Jan 2005 20:47:56 -0500
To: "KAMADA Ken'ichi" <kamada@nanohz.org>
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: -4.9
X-Spam-Flag: NO
X-Scanned-By: MIMEDefang 2.42
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


On Jan 27, 2005, at 19:07, KAMADA Ken'ichi wrote:
> 1) omit the checksum field (splicing the header and payloads directly),
> 2) zero out the Length and CksumLen fields because we can't know
>    those lengthes in advance.
>
> My consern/questions are
> - 2) makes me nervous because I don't know whether it makes some
>   kinds of attacks easy (e.g. adding junk data at the end of payloads
>   in order to collide the checksum).

How about including length-without-checksum in the calculation of the 
checksum, instead of a zero?

> - Will required-to-implement checksums never change in the future?

I believe that's the case.

The required-to-implement field was intended to deal with the lack of 
checksum negotiation in Kerberos.  We assert that if you know 
encryption type X is supported, then you know that checksum type Y is 
also supported, and thus you're free to use it.  If we go back and 
change it, we'd be retroactively changing the implementation 
requirements of code (theoretically) already deployed.

It might not hurt to include the checksum type anyways.

> - Thinking about 1), placing the checksum at the end of the packet
>   is more reasonable?

It might be, yes.

> BTW, is a statement like "KINK does not support encryption types with
> such variable length checksums" reasonable in the sense of Kerberos?

I would lean towards "no", because it makes things more complex and 
treats Kerberos as less of a black box.  I suppose it's possible, but 
in my opinion should be avoided.

> Is there any such checksums at this moment?

None outside my imagination.  I could write one up if you like. :-)

This one would be easy enough:
   confounder = random 128-bit block
   h = HMAC-SHA512(confounder | key-usage | msg, key)
   len = random multiple of 8 between 128 and 512
   checksum = confounder | h[1..len]

It's non-deterministic, and the length varies from 256 to 640 bits.  
I'd have to check, but offhand I think it would comply with the 
Kerberos checksum requirements.

Ken



From owner-ietf-kink@mail.vpnc.org  Thu Jan 27 21:00:22 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18833
	for <kink-archive@lists.ietf.org>; Thu, 27 Jan 2005 20:10:59 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0S06aPq069208;
	Thu, 27 Jan 2005 16:06:36 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0S06asr069207;
	Thu, 27 Jan 2005 16:06:36 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from nasten.nanohz.org (usen-220x218x5x242.ap-US00.usen.ad.jp [220.218.5.242])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0S06ZJs069164
	for <ietf-kink@vpnc.org>; Thu, 27 Jan 2005 16:06:35 -0800 (PST)
	(envelope-from kamada@nanohz.org)
Received: from nasten.nanohz.org (localhost [127.0.0.1])
	by nasten.nanohz.org (Postfix) with ESMTP id CD9355
	for <ietf-kink@vpnc.org>; Fri, 28 Jan 2005 09:06:17 +0900 (JST)
Received: from mitana.nanohz.org ([2001:240:2:0:202:8aff:fefa:bec0])
	by nasten.nanohz.org (smtpsugar 1.1) with ESMTPA
	id 4nWanj; Fri, 28 Jan 2005 09:06:17 +0900 (JST)
Date: Fri, 28 Jan 2005 09:07:16 +0900
Message-ID: <20050128090716FA%kamada@nanohz.org>
From: "KAMADA Ken'ichi" <kamada@nanohz.org>
To: ietf-kink@vpnc.org
Subject: Re: Checksum (Re: KINK issue list)
In-Reply-To: <71f7d1221376acbc8485b84b11f8aaf4@mit.edu>
References: <20050120102450Q.sakane@kame.net>
	<20050120103639RZ%kamada@nanohz.org>
	<20050120110448RR%kamada@nanohz.org>
	<20050127171645FM%kamada@nanohz.org>
	<71f7d1221376acbc8485b84b11f8aaf4@mit.edu>
User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.3.50
 (i386-unknown-netbsdelf2.0G) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


Thank you for your comments.

At Thu, 27 Jan 2005 10:34:03 -0500,
Ken Raeburn <raeburn@MIT.EDU> wrote:
> 
> On Jan 27, 2005, at 03:16, KAMADA Ken'ichi wrote:
> > My main concern with this proposal is whether all future etypes
> > will be based on simplified profile (have HMAC, I mean) or not.
> 
> I think it's safe to say that eventually we will see new encryption 
> types that do not use the simplified profile.  We may also see some 
> that do, of course.  But with the variety of authenticated-encryption 
> modes being produced and analyzed, it would make sense for us to stop 
> constructing our own.  So I'd expect some future cryptosystem to be 
> based on EAX, CCM, or some other such mode.
> 
> In order for KINK to not require updates for these future 
> cryptosystems, you'd need to be able to say now how to determine what 
> kind of checksum is to be used.

I agree.

> The only tricky issue in dealing with the required-to-implement 
> checksum type should be the lack of a fixed size output.  Is it that 
> hard to work around?  (Maybe omit the checksum field when computing the 
> checksum?)

I think it's not so hard in itself.  When computing the checksum,
we will need to
1) omit the checksum field (splicing the header and payloads directly),
2) zero out the Length and CksumLen fields because we can't know
   those lengthes in advance.

My consern/questions are
- 2) makes me nervous because I don't know whether it makes some
  kinds of attacks easy (e.g. adding junk data at the end of payloads
  in order to collide the checksum).
- Will required-to-implement checksums never change in the future?
- Thinking about 1), placing the checksum at the end of the packet
  is more reasonable?


BTW, is a statement like "KINK does not support encryption types with
such variable length checksums" reasonable in the sense of Kerberos?
Is there any such checksums at this moment?

-- 
KAMADA Ken'ichi <kamada@nanohz.org>



From owner-ietf-kink@mail.vpnc.org  Thu Jan 27 22:42:25 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA29938
	for <kink-archive@lists.ietf.org>; Thu, 27 Jan 2005 22:42:25 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0S3dci1086203;
	Thu, 27 Jan 2005 19:39:38 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0S3dcdx086202;
	Thu, 27 Jan 2005 19:39:38 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from papa.tanu.org (kame195.kame.net [203.178.141.195])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0S3dWx7086193
	for <ietf-kink@vpnc.org>; Thu, 27 Jan 2005 19:39:37 -0800 (PST)
	(envelope-from sakane@kame.net)
Received: from localhost (cp.64translator.com [202.214.123.2])
	by papa.tanu.org (8.12.9/8.12.8) with ESMTP id j0S3dhhB083302
	for <ietf-kink@vpnc.org>; Fri, 28 Jan 2005 12:39:44 +0900 (JST)
	(envelope-from sakane@kame.net)
To: ietf-kink@vpnc.org
Subject: racoon2 release
X-Mailer: Cue version 0.8 (041108-2350/sakane)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Message-Id: <20050128124009Y.sakane@kame.net>
Date: Fri, 28 Jan 2005 12:40:09 +0900
From: Shoichi Sakane <sakane@kame.net>
X-Dispatcher: imput version 20030322(IM144)
Lines: 19
X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c
	on papa.tanu.org
X-Virus-Status: Clean
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


This is from the racoon2 project.

We are ready to release "racoon2" a IPsec key management system.
"racoon2" is a system to exchange and to install security parameters
for the IPsec.  This is provided by the Racoon2 Project in the WIDE
Project, Japan.  The project aims to provide the IPsec system for
FreeBSD, NetBSD and Linux.

We have removed our IKEv2 code from the release because we have an IPR
issue related to IKEv2.  We will release it after the issue will
be solved.  KINK is only supported in the release currently.

You can get the tarball from:
        ftp://ftp.kame.net/pub/racoon2/racoon2-20050128b.tgz

Please ask to racoon2@kame.net if you have any question.

regards,



From owner-ietf-kink@mail.vpnc.org  Fri Jan 28 00:21:15 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA07912
	for <kink-archive@lists.ietf.org>; Fri, 28 Jan 2005 00:21:14 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0S5IU62092344;
	Thu, 27 Jan 2005 21:18:31 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0S5IU0I092343;
	Thu, 27 Jan 2005 21:18:30 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from miyazawa.org (usen-221x116x13x66.ap-US01.usen.ad.jp [221.116.13.66])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0S5IPO9092326
	for <ietf-kink@vpnc.org>; Thu, 27 Jan 2005 21:18:25 -0800 (PST)
	(envelope-from kazunori@miyazawa.org)
Received: from [IPv6:2001:240:2:0:25ec:ada6:9996:e961] ([2001:240:2:0:25ec:ada6:9996:e961])
  (AUTH: LOGIN kazunori, SSL: TLSv1/SSLv3,256bits,AES256-SHA)
  by miyazawa.org with esmtp; Fri, 28 Jan 2005 14:17:53 +0900
  id 00007D92.41F9CB01.000056B2
Message-ID: <41F9CAE7.3070301@miyazawa.org>
Date: Fri, 28 Jan 2005 14:17:27 +0900
From: Kazunori Miyazawa <kazunori@miyazawa.org>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: Shoichi Sakane <sakane@kame.net>
CC: ietf-kink@vpnc.org
Subject: Re: KINK should referenece to IKEv2?
References: <tslllanc1qa.fsf@cz.mit.edu> <20050127143507Z.sakane@kame.net>
In-Reply-To: <20050127143507Z.sakane@kame.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


Shoichi Sakane wrote:
>>Speaking as an AD, if 2401bis is approved by IETF 62, Kink will be
>>based on 2401bis.  If not, then it depends on where 2401bis is, where
>>Kink is, and how fast things are moving.
> 
> 
> I dont understand why KINK will be based on 2401bis when 2401bis
> is approved by IETF62.  There are lots of platforms based on 2401.
> KINK should be based on 2401 in order to deploy it.  If the market
> will not choice 2401bis and if a kink implementation based on 2401bis
> does not work on a platform based on 2401, then KINK will not deploy.
> 
> it is not easy to know how difference between 2401bis and 2401,
> and it is not easy to know if a key management daemon based on
> 2401bis will work on a platform based on 2401.  so I said in previous
> mail that we should make kink based on 2401 then make kink based on
> 2401bis.  kink header has a version field.
> 

I agree with Sakane-san.

I think if kink is based on 2401bis, it would use IKEv2 instead of ISAKMP.
If it uses IKEv2, I guess there are conflicts which are rekeying and dead peer
handling because IKEv1 does not mention those process and KINK specifies it by
it self. Changing for IKEv2 and resolving new issues need a long time.
I think we should go with 2401.

--
Kazunori Miyazawa



From owner-ietf-kink@mail.vpnc.org  Fri Jan 28 02:25:01 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28742
	for <kink-archive@lists.ietf.org>; Fri, 28 Jan 2005 02:25:00 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0S7Mobx024580;
	Thu, 27 Jan 2005 23:22:50 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0S7Mogl024579;
	Thu, 27 Jan 2005 23:22:50 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from march.taca.jp (vbox.nezu.wide.ad.jp [203.178.142.195])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0S7MnHH024567
	for <ietf-kink@vpnc.org>; Thu, 27 Jan 2005 23:22:50 -0800 (PST)
	(envelope-from nov@tahi.org)
Received: from localhost (vbox.nezu.wide.ad.jp [203.178.142.195])
	by march.taca.jp (Postfix) with ESMTP
	id 4271F1FBC2; Fri, 28 Jan 2005 15:08:04 +0900 (JST)
Date: Fri, 28 Jan 2005 15:08:03 +0900 (JST)
Message-Id: <20050128.150803.10289869.nov@tahi.org>
To: kazunori@miyazawa.org
Cc: sakane@kame.net, ietf-kink@vpnc.org
Subject: Re: KINK should referenece to IKEv2?
From: Nobuo OKABE <nov@tahi.org>
In-Reply-To: <41F9CAE7.3070301@miyazawa.org>
References: <tslllanc1qa.fsf@cz.mit.edu>
	<20050127143507Z.sakane@kame.net>
	<41F9CAE7.3070301@miyazawa.org>
X-Mailer: Mew version 4.1 on Emacs 20.7 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


From: Kazunori Miyazawa <kazunori@miyazawa.org>
Subject: Re: KINK should referenece to IKEv2?
Date: Fri, 28 Jan 2005 14:17:27 +0900

> 
> Shoichi Sakane wrote:
> >>Speaking as an AD, if 2401bis is approved by IETF 62, Kink will be
> >>based on 2401bis.  If not, then it depends on where 2401bis is, where
> >>Kink is, and how fast things are moving.
> > 
> > 
> > I dont understand why KINK will be based on 2401bis when 2401bis
> > is approved by IETF62.  There are lots of platforms based on 2401.
> > KINK should be based on 2401 in order to deploy it.  If the market
> > will not choice 2401bis and if a kink implementation based on 2401bis
> > does not work on a platform based on 2401, then KINK will not deploy.
> > 
> > it is not easy to know how difference between 2401bis and 2401,
> > and it is not easy to know if a key management daemon based on
> > 2401bis will work on a platform based on 2401.  so I said in previous
> > mail that we should make kink based on 2401 then make kink based on
> > 2401bis.  kink header has a version field.
> > 
> 
> I agree with Sakane-san.
> 
> I think if kink is based on 2401bis, it would use IKEv2 instead of ISAKMP.
> If it uses IKEv2, I guess there are conflicts which are rekeying and dead peer
> handling because IKEv1 does not mention those process and KINK specifies it by
> it self. Changing for IKEv2 and resolving new issues need a long time.
> I think we should go with 2401.

I also agree with Sakane-san.

And I have an observation.

    Our discussions will be more productive
    if we can categorize issues.

    Some issues were based on Kerberos clarification
    and/or kcrypt, some were on 2401bis,
    some were on IKEv2 and so on.

    We can go forward with Kerberos related issues
    even if we can not solve 2401bis and/or IKEv2 related issues
    which may need long time to be solved.

----- nobuo



From owner-ietf-kink@mail.vpnc.org  Fri Jan 28 02:26:38 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28995
	for <kink-archive@lists.ietf.org>; Fri, 28 Jan 2005 02:26:37 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0S7KfnN023776;
	Thu, 27 Jan 2005 23:20:41 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0S7KfhK023775;
	Thu, 27 Jan 2005 23:20:41 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from biscayne-one-station.mit.edu (BISCAYNE-ONE-STATION.MIT.EDU [18.7.7.80])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0S7JqnQ023252
	for <ietf-kink@vpnc.org>; Thu, 27 Jan 2005 23:20:35 -0800 (PST)
	(envelope-from raeburn@MIT.EDU)
Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103])
	by biscayne-one-station.mit.edu (8.12.4/8.9.2) with ESMTP id j0S6vIEY011501;
	Fri, 28 Jan 2005 01:57:19 -0500 (EST)
Received: from [18.101.0.226] ([18.101.0.226])
	(authenticated bits=0)
        (User authenticated as raeburn@ATHENA.MIT.EDU)
	by outgoing.mit.edu (8.12.4/8.12.4) with ESMTP id j0S6vE0a014547
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT);
	Fri, 28 Jan 2005 01:57:17 -0500 (EST)
In-Reply-To: <20050128124009Y.sakane@kame.net>
References: <20050128124009Y.sakane@kame.net>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <6199f4b3455738c33a45787a74a5cf9e@mit.edu>
Content-Transfer-Encoding: 7bit
Cc: ietf-kink@vpnc.org
From: Ken Raeburn <raeburn@MIT.EDU>
Subject: Re: racoon2 release
Date: Fri, 28 Jan 2005 01:57:13 -0500
To: Shoichi Sakane <sakane@kame.net>
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: -4.9
X-Spam-Flag: NO
X-Scanned-By: MIMEDefang 2.42
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


On Jan 27, 2005, at 22:40, Shoichi Sakane wrote:
> We have removed our IKEv2 code from the release because we have an IPR
> issue related to IKEv2.  We will release it after the issue will
> be solved.  KINK is only supported in the release currently.

I may be being overly picky, but: KINK isn't finalized.  KINK would 
presumably be the name of the final version of the protocol.  So it 
wouldn't be correct to say that it supports KINK, but instead you 
should indicate that it supports a specific draft.  And I expect that 
the final version will not be 100% compatible with the current draft 
(if only in the handling of some of the crypto aspects I've complained 
about), so it would make sense to advise users of that fact as well, 
and plan for either an incompatible change down the road, or support 
for both draft and final versions in some future release.

That said, I think it's great that you're doing this.  Thank you!

Ken



From owner-ietf-kink@mail.vpnc.org  Fri Jan 28 16:16:38 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14485
	for <kink-archive@lists.ietf.org>; Fri, 28 Jan 2005 16:16:35 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0SLANHP092118;
	Fri, 28 Jan 2005 13:10:23 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0SLANnu092117;
	Fri, 28 Jan 2005 13:10:23 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from cz.mit.edu (STRATTON-FOUR.MIT.EDU [18.187.5.4])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0SLAIeS092106
	for <ietf-kink@vpnc.org>; Fri, 28 Jan 2005 13:10:18 -0800 (PST)
	(envelope-from hartmans@mit.edu)
Received: by cz.mit.edu (Postfix, from userid 8042)
	id E8D4DE0063; Fri, 28 Jan 2005 16:10:18 -0500 (EST)
To: Kazunori Miyazawa <kazunori@miyazawa.org>
Cc: Shoichi Sakane <sakane@kame.net>, ietf-kink@vpnc.org
Subject: Re: KINK should referenece to IKEv2?
References: <tslllanc1qa.fsf@cz.mit.edu> <20050127143507Z.sakane@kame.net>
	<41F9CAE7.3070301@miyazawa.org>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Fri, 28 Jan 2005 16:10:18 -0500
In-Reply-To: <41F9CAE7.3070301@miyazawa.org> (Kazunori Miyazawa's message of
 "Fri, 28 Jan 2005 14:17:27 +0900")
Message-ID: <tslis5htg3p.fsf@cz.mit.edu>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


>>>>> "Kazunori" == Kazunori Miyazawa <kazunori@miyazawa.org> writes:

    Kazunori> Shoichi Sakane wrote:
    >>> Speaking as an AD, if 2401bis is approved by IETF 62, Kink
    >>> will be based on 2401bis.  If not, then it depends on where
    >>> 2401bis is, where Kink is, and how fast things are moving.
    >> I dont understand why KINK will be based on 2401bis when
    >> 2401bis is approved by IETF62.  There are lots of platforms
    >> based on 2401.  KINK should be based on 2401 in order to deploy
    >> it.  If the market will not choice 2401bis and if a kink
    >> implementation based on 2401bis does not work on a platform
    >> based on 2401, then KINK will not deploy.  it is not easy to
    >> know how difference between 2401bis and 2401, and it is not
    >> easy to know if a key management daemon based on 2401bis will
    >> work on a platform based on 2401.  so I said in previous mail
    >> that we should make kink based on 2401 then make kink based on
    >> 2401bis.  kink header has a version field.
    >> 

    Kazunori> I agree with Sakane-san.

    Kazunori> I think if kink is based on 2401bis, it would use IKEv2
    Kazunori> instead of ISAKMP.  

That would be a valid way of making Kink based on 2401bis.  It seems
like a lot of work and I am not sure it is in the best interest of the
working group to choose to make Kink work with 2401bis that way.

Again, I did present the assumptions under which I decided to require
2401bis.  You would need to show me that one of those assumptions is
wrong in order to convince me to change my mind.

--Sam



From owner-ietf-kink@mail.vpnc.org  Fri Jan 28 21:27:00 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14360
	for <kink-archive@lists.ietf.org>; Fri, 28 Jan 2005 21:26:59 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0T2Jl2l010433;
	Fri, 28 Jan 2005 18:19:47 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0T2Jl4Z010432;
	Fri, 28 Jan 2005 18:19:47 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from luminous.mit.edu (LUMINOUS.MIT.EDU [18.101.1.61])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0T2Jk4Z010426
	for <ietf-kink@vpnc.org>; Fri, 28 Jan 2005 18:19:46 -0800 (PST)
	(envelope-from hartmans@mit.edu)
Received: by luminous.mit.edu (Postfix, from userid 1000)
	id 1963F76C87; Fri, 28 Jan 2005 21:19:39 -0500 (EST)
To: ietf-kink@vpnc.org
Subject: AD Review: draft-ietf-kink-kink [starting at section 5]
From: Sam Hartman <hartmans-ietf@mit.edu>
Message-Id: <20050129021939.1963F76C87@luminous.mit.edu>
Date: Fri, 28 Jan 2005 21:19:39 -0500 (EST)
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


General issues:

[**] Versioning: what happens when a receiver receives a major or
minor version of the kink or qm that is inconsistent with this
document?  What about unknown payload types?


[**] U2u: I think we need to look at how u2u works at various parts of
the protocol.  In particular I'm concerned about choosing the right
u2u principal, dealing with cross-realm u2u and dealing with
recovering from reboots.  We should confirm all these work out.


Section 5:




     o  DOI (4 octets) - The domain of interpretation. All DOI's must be
	registered with the IANA in the "Assigned Numbers" RFC [STD-2].

Cite a specific registry please.  IANA registries are typically named, and a URL reference would probably be appropriate.


     o  Reserved (15 bits) --  Reserved and must be zero

Must be zero on send, must be ignored by receiver.


     o  CksumLen (2 octets) -- CksumLen is the length in octets of the
	keyed hash of the message. A CksumLen of zero implies that the
	message is unauthenticated. Note that as with payload padding, the
	length here denotes the actual number of octets of the checksum
	structure not including any padding required.


If I understand this text correctly, the length would be set to 6 if I
had a 6-byte checksum padded outto 8 bytes.  How would kink find out
about those two bytes of padding and know to skip them?

In a kcrypto universe I believe this length should just be the length
of the output of the get_mic operation.  Reading later, perhaps this
text is only talking about kink padding  not crypto-system padding.
If so, then please just clarify that you mean the padding discussed in 5.1.

[**] The checksum length is non-deterministic.


[**] The description of the checksum says that the session key of the
ticket is used.  That's a way to do it, but the working group should
explain why it has chosen to ignore the subsession key.

[**] The document claims that the transaction id is not used for
replay detection because Kerberos provides that.  How is that true?
The authenticator is protected against replays but how is the rest of
the message bound to that specific authenticator instead of to a
session key of a ticket?

The cksum field should be the output of the get_mic operation and the
verify_mic operation should be used to verify it.  I believe
appropriate text has already been suggested on the list.

Why is the next payload in the message header one byte, but the next
payload in the payload header two bytes?  If this is not a
documentation bug, it should probably be called out so people know not
to assign payload ids greater than 255.



Section 5.1.2:

[**] How do I discover the FQDN of my remote peer?   SPD
entries are configured in terms of  IP addresses.  If you  want to
store an identity in the PAD, why not store a principal instead of a
hostname.

[**] How do I authorize which service I'm talking to in the u2u case.
I.E. how do I know what principals are authorized for a particular SPD
entry?

	tion information across different restarts. The format of this
	fields is network order encoding of the standard posix four octet
	time stamp.


Perhaps you need a description of the time stamp?  I recall there
being such a description in draft-housley-binarytime-xx.


Section 5.1.4:

[**] Why should a sender send only those errors?  I'm mostly asking
for an explanation to be given to me or to be added to the document
rather than liberalization of the requirement.



     KINK implementations MUST make use of keyed Kerberos errors when  the
     appropriate  service  key  is available as specified in [KRBREVS]. In
     particular, clock  skew  errors  MUST  be  integrity  protected.  For
     unauthenticated  Kerberos  errors,  the receiver MAY choose to act on
     them, but SHOULD take precautions against make-work kinds of attacks.

Remove paragraph.


Section 5.1.5:

[**] Please Consider how this works in the cross-realm case.
I.E. make sure you end up with the right ticket on the right side.  I
believe this text assumes that you need a ticket in a realm close to
the client; I think that for things to work you actually need a realm
close to the server.  Work through the message flows and make sure the
KDC doing the decryption actually has the necessary keys and then
adjust the document if necessary so the right KDC is used.

The document needs to clearly indicate what error code is used in the
case when the responder cannot get a ticket because some cross-realm
key is missing.  In general we want it to be possible for an initiator
to try several identities until the initiator finds the right one that
has a shared key.

Section 5.1.8: [**] Please use the output of the kcrypto encrypt
operation directly.  Of most importance is to make sure that all
kcrypto enctypes will work even if it is not possible to decompose the
kcrypto checksum from the encrypted data.  This probably means that in
some cases you will have double checksums.
You also need to deal with making sure you can determine the length of
the plaintext.

Text should probably indacte that next payload must be none.

Section 6.1:


   o    IKE Quick Mode (phase 2) uses the hash algorithm used in main
        mode (phase 1) to generate the keying material. KINK MUST use
        the hashing algorithm specified in the session ticket's etype.

[**] This checksum may not be deterministic and is probably not
appropriate for use in setting up a key.  A PRF is provided, although
depending on how the hash is used the PRF may or may not be a suitable
replacement.  There has been significant discussion within krb-wg on
when the PRF is appropriate and when it is not.  This discussion
centered around key determination in pkinit.


Section 6.8:

What happens if a peer that implements the KE payloads communicates
with a peer that does not.  Specify the behavior in sufficient detail
to guarantee interoperability.


Section 7.1:

     defined in the following sections.  The checksum in the KRB-ERROR
     message is not used, since the KINK header already contains a check-
     sum field.

Drop reference to krb-error checksum.


Section 8:

I don't understand what this section says well enough to determine
whether it works with kcrypto.


Section 10.1:

This should not go in the security considartions section.  It is
really more about IPsec architectural considerations than security
considerations.

This text needs to take into account 2401bis.  In particular it needs
to be properly split between SPD considerations and PAD
considerations.


Section 11:

Needs work.  You may want to stop by tthe IANA office hours and ask
them for advice.  They are generally quite good at working with
authors to figure out how things need to be specified.



From owner-ietf-kink@mail.vpnc.org  Sat Jan 29 00:16:55 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA25762
	for <kink-archive@lists.ietf.org>; Sat, 29 Jan 2005 00:16:54 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0T5Duox021498;
	Fri, 28 Jan 2005 21:13:56 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0T5DucS021497;
	Fri, 28 Jan 2005 21:13:56 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from biscayne-one-station.mit.edu (BISCAYNE-ONE-STATION.MIT.EDU [18.7.7.80])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0T5DtKH021490
	for <ietf-kink@vpnc.org>; Fri, 28 Jan 2005 21:13:56 -0800 (PST)
	(envelope-from raeburn@MIT.EDU)
Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103])
	by biscayne-one-station.mit.edu (8.12.4/8.9.2) with ESMTP id j0T5Drq6029655;
	Sat, 29 Jan 2005 00:13:53 -0500 (EST)
Received: from [18.101.0.226] ([18.101.0.226])
	(authenticated bits=0)
        (User authenticated as raeburn@ATHENA.MIT.EDU)
	by outgoing.mit.edu (8.12.4/8.12.4) with ESMTP id j0T5Db0a010200
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT);
	Sat, 29 Jan 2005 00:13:38 -0500 (EST)
In-Reply-To: <20050129021939.1963F76C87@luminous.mit.edu>
References: <20050129021939.1963F76C87@luminous.mit.edu>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <49550b4eb40f91d161272fcd0966e59d@mit.edu>
Content-Transfer-Encoding: 7bit
Cc: ietf-kink@vpnc.org
From: Ken Raeburn <raeburn@MIT.EDU>
Subject: Re: AD Review: draft-ietf-kink-kink [starting at section 5]
Date: Sat, 29 Jan 2005 00:13:31 -0500
To: Sam Hartman <hartmans-ietf@MIT.EDU>
X-Mailer: Apple Mail (2.619.2)
X-Spam-Score: -4.9
X-Spam-Flag: NO
X-Scanned-By: MIMEDefang 2.42
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


On Jan 28, 2005, at 21:19, Sam Hartman wrote:
> Section 5.1.5:
>
> [**] Please Consider how this works in the cross-realm case.
> I.E. make sure you end up with the right ticket on the right side.  I
> believe this text assumes that you need a ticket in a realm close to
> the client; I think that for things to work you actually need a realm
> close to the server.  Work through the message flows and make sure the
> KDC doing the decryption actually has the necessary keys and then
> adjust the document if necessary so the right KDC is used.

In working this through, I suggest attention also be paid to whether 
anything happening is specific to KINK, or if we're just working 
through issues of cross-realm user-to-user authentication that 
rfc1510/clarifications might not have explained adequately.  (We use 
user-to-user rarely enough in most situations, I don't know if anyone's 
actually using it in the cross-realm case.)

Ken



From owner-ietf-kink@mail.vpnc.org  Sun Jan 30 19:40:48 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17466
	for <kink-archive@lists.ietf.org>; Sun, 30 Jan 2005 19:40:46 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0V0YXGw096201;
	Sun, 30 Jan 2005 16:34:33 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0V0YX5W096200;
	Sun, 30 Jan 2005 16:34:33 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from nasten.nanohz.org (usen-220x218x5x242.ap-US00.usen.ad.jp [220.218.5.242])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0V0YW2U096173
	for <ietf-kink@vpnc.org>; Sun, 30 Jan 2005 16:34:33 -0800 (PST)
	(envelope-from kamada@nanohz.org)
Received: from nasten.nanohz.org (localhost [127.0.0.1])
	by nasten.nanohz.org (Postfix) with ESMTP id 403705
	for <ietf-kink@vpnc.org>; Mon, 31 Jan 2005 09:34:07 +0900 (JST)
Received: from mitana.nanohz.org ([2001:240:2:0:202:8aff:fefa:bec0])
	by nasten.nanohz.org (smtpsugar 1.1) with ESMTPA
	id 3v8Ng2; Mon, 31 Jan 2005 09:34:07 +0900 (JST)
Date: Mon, 31 Jan 2005 09:35:09 +0900
Message-ID: <20050131093509FD%kamada@nanohz.org>
From: "KAMADA Ken'ichi" <kamada@nanohz.org>
To: ietf-kink@vpnc.org
Subject: Re: Checksum (Re: KINK issue list)
In-Reply-To: <4862abd2ff60e5469610a75831516214@mit.edu>
References: <20050120102450Q.sakane@kame.net>
	<20050120103639RZ%kamada@nanohz.org>
	<20050120110448RR%kamada@nanohz.org>
	<20050127171645FM%kamada@nanohz.org>
	<71f7d1221376acbc8485b84b11f8aaf4@mit.edu>
	<20050128090716FA%kamada@nanohz.org>
	<4862abd2ff60e5469610a75831516214@mit.edu>
User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.3.50
 (i386-unknown-netbsdelf2.0G) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


At Thu, 27 Jan 2005 20:47:56 -0500,
Ken Raeburn <raeburn@MIT.EDU> wrote:
> 
> > - 2) makes me nervous because I don't know whether it makes some
> >   kinds of attacks easy (e.g. adding junk data at the end of payloads
> >   in order to collide the checksum).
> 
> How about including length-without-checksum in the calculation of the 
> checksum, instead of a zero?

This seems to work.

So current proposed solution is:
- Use required-to-implement checksum type determined by the etype.
- Use get_mic or verify_mic function to generate or verify the checksum.
- Omit the checksum field before calculation.
- The Length field is filled with the packet length without checksum and
  the CksumLen field is zeroed out before the calculation.

-- 
KAMADA Ken'ichi <kamada@nanohz.org>



From owner-ietf-kink@mail.vpnc.org  Sun Jan 30 19:54:46 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18161
	for <kink-archive@lists.ietf.org>; Sun, 30 Jan 2005 19:54:45 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0V0opj2097059;
	Sun, 30 Jan 2005 16:50:51 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0V0op5l097058;
	Sun, 30 Jan 2005 16:50:51 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from nasten.nanohz.org (usen-220x218x5x242.ap-US00.usen.ad.jp [220.218.5.242])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0V0ooYf097052
	for <ietf-kink@vpnc.org>; Sun, 30 Jan 2005 16:50:50 -0800 (PST)
	(envelope-from kamada@nanohz.org)
Received: from nasten.nanohz.org (localhost [127.0.0.1])
	by nasten.nanohz.org (Postfix) with ESMTP id 099CA5
	for <ietf-kink@vpnc.org>; Mon, 31 Jan 2005 09:50:50 +0900 (JST)
Received: from mitana.nanohz.org ([2001:240:2:0:202:8aff:fefa:bec0])
	by nasten.nanohz.org (smtpsugar 1.1) with ESMTPA
	id 2LscsL; Mon, 31 Jan 2005 09:50:50 +0900 (JST)
Date: Mon, 31 Jan 2005 09:51:54 +0900
Message-ID: <20050131095154FY%kamada@nanohz.org>
From: "KAMADA Ken'ichi" <kamada@nanohz.org>
To: ietf-kink@vpnc.org
Subject: Re: AD Review: draft-ietf-kink-kink [starting at section 5]
In-Reply-To: <20050129021939.1963F76C87@luminous.mit.edu>
References: <20050129021939.1963F76C87@luminous.mit.edu>
User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.3.50
 (i386-unknown-netbsdelf2.0G) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


At Fri, 28 Jan 2005 21:19:39 -0500 (EST),
Sam Hartman <hartmans-ietf@mit.edu> wrote:
> 
> Section 5.1.2:
> 
> [**] How do I discover the FQDN of my remote peer?   SPD
> entries are configured in terms of  IP addresses.  If you  want to
> store an identity in the PAD, why not store a principal instead of a
> hostname.

I interpreted the text as a naming convention, not how a implementation
get a peer's principal name.  So I think it is an implementation issue
whether a principal name is generated from a FQDN or got directly from
the PAD.

-- 
KAMADA Ken'ichi <kamada@nanohz.org>



From owner-ietf-kink@mail.vpnc.org  Mon Jan 31 05:02:59 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07904
	for <kink-archive@lists.ietf.org>; Mon, 31 Jan 2005 05:02:58 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0V9sE9K006737;
	Mon, 31 Jan 2005 01:54:20 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0V9sEbE006724;
	Mon, 31 Jan 2005 01:54:14 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from nasten.nanohz.org (usen-220x218x5x242.ap-US00.usen.ad.jp [220.218.5.242])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0V9rkld005709
	for <ietf-kink@vpnc.org>; Mon, 31 Jan 2005 01:54:10 -0800 (PST)
	(envelope-from kamada@nanohz.org)
Received: from nasten.nanohz.org (localhost [127.0.0.1])
	by nasten.nanohz.org (Postfix) with ESMTP id C2D3C5
	for <ietf-kink@vpnc.org>; Mon, 31 Jan 2005 17:05:42 +0900 (JST)
Received: from mitana.nanohz.org ([2001:240:2:0:202:8aff:fefa:bec0])
	by nasten.nanohz.org (smtpsugar 1.1) with ESMTPA
	id 0Nhxgd; Mon, 31 Jan 2005 17:05:42 +0900 (JST)
Date: Mon, 31 Jan 2005 17:06:44 +0900
Message-ID: <20050131170644FW%kamada@nanohz.org>
From: "KAMADA Ken'ichi" <kamada@nanohz.org>
To: ietf-kink@vpnc.org
Subject: KINK issue list rev.2
User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.3.50
 (i386-unknown-netbsdelf2.0G) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


AD Review is merged.
Numbered.
User-to-User issues and cross-realm issues are not yet well ordered.


[**] Indicates an issue considered substantive.
[-] Indicates an editorial issue.
(2401bis): depends on 2401 vs 2401bis


#1 [**] Versioning

	what happens when a receiver receives a major or
	minor version of the kink or qm that is inconsistent with this
	document?  What about unknown payload types?  (Sam Hartman)

	QM version is discussed in section 12 (Forward Compatibility
	Considerations).

	- KINK version
		return error (KINK_INVMAJ, KINK_INVMIN)
	- QM versoin
		already specified in section 12.
	- KINK payload type
		return error (KINK_PROTOERR)
	- ISAKMP payload type
		return error (ISAKMP INVALID-PAYLOAD-TYPE)
		(describe each Notify type usage like ikev2 spec.)

	Specify the behavior when the error is not authenticated
	in the Security Consideration section.


#2 [**] U2U

	I think we need to look at how u2u works at various parts of
	the protocol.  In particular I'm concerned about choosing the right
	u2u principal, dealing with cross-realm u2u and dealing with
	recovering from reboots.  We should confirm all these work out.
	(Sam Hartman)


#3 [**] user-to-user (section 3, 4.2, and 5.1.2)

	It seems like the
	server tells the client what principal to authenticate to, but this
	principal is not properly authorized.  (Sam Hartman)

	More examination of user-to-user case, especially situations where 
	it might *not* be two PKINIT clients, which section 3 says is possible. 
	(BTW, in the Kerberos docs, it's "user-to-user", not "user-user".)
	(Ken Raeburn)

	Verifying remotely supplied identity, as Sam raised earlier.
	(Ken Raeburn)

	In the user-to-user case with TGTs, I think the KINK draft may be 
	over-specifying things that should be dealt with at the Kerberos level. 
	If things are underspecified in Kerberos Clarifications, let's deal 
	with that.  (Ken Raeburn)

	Section 4.2:
	[**] How will the initiator determine whether it will be able to get a
	TGT?  I think policy considerations of when to use u2u and
	authorization considerations of what u2u principals are authorized are
	underspecified in the draft.
	(Sam Hartman)

	[**] Make sure the descriptions of u2u work correctly in the
	cross-realm case.
	(Sam Hartman)

	Section 5.1.2:
	[**] How do I authorize which service I'm talking to in the u2u case.
	I.E. how do I know what principals are authorized for a particular SPD
	entry?  (Sam Hartman)


#4 [**](2401bis) CREATE command from the aspect of 2401bis (section 4.3)

	I need explicit review from the IPsec reviewer of this section to
	make sure it is compatible with 2401bis.


#37 [**] Difference between IKE and KINK on CREATE command (section 4.3)

	IN addition, any differences
	between how this works and how IKE would set up the same SA need to be
	called out.  It is fine for there to be differences, but I want to
	make sure the working group explicitly decided the differences are a
	good thing.

	I'm somewhat concerned that 4.3 is not specific enough to describe
	exactly what key gets set up.  I.E. I'm concerned it may not be
	detailed enough for interoperable implementations.
	(Sam Hartman)


#5 [*] When 3-way, is responder's nonce MUST or SHOULD? (section 4.3 and 7.3)

	Sec 4.3 and 7.3 use SHOULD and MUST respectively regarding when the 
	nonce should be used.  If the circumstances they're describing are 
	different, that's okay, but if so, I missed it on first reading.
	(Ken Raeburn)


#6 [*] Half open (section 4.4)
(solution proposed)

	IPsec does not allow half-open security associations any more as far
	as I can tell in 2401bis.  So it's not just for simplicity, but for
	model conformance.  (Sam Hartman)

	Proposed solution:
	remove the phrase "for simplicity".
	(Message-ID: <tslu0pbc3h9.fsf@cz.mit.edu>)


#7 [**] DPD & STATUS (section 4.4.2 and 4.5)

	[**] Discuss status message, rebooting peers and u2u.  This looks a
	lot like the IKE case where you lose all cryptographic context to me.
	(Sam Hartman)


#8 [*] CksumLen (section 5)

	Diagram indicates one octet for cksumlen, but the text (and 
	kcrypto specifications) say it should be two.

	Clarify that you mean the padding discussed in 5.1 (KINK Padding
	Rules), not crypto-system padding.  (Sam Hartman)


#9 [**] etype does not directly indicate checksum type (section 5)
(solution proposed)

	a key's encryption type does not directly indicate 
	a checksum type, it indicates an encryption(-with-integrity-protection) 
	scheme, which does include a required-to-implement checksum type
	(Ken Raeburn)

	Proposed solutions are:
	- Use required-to-implement checksum type determined by the etype.
	- Use get_mic or verify_mic function to generate or verify the checksum.
	- Omit the checksum field before calculation.
	- The Length field is filled with the packet length without checksum and
	  the CksumLen field is zeroed out before the calculation.
	(Message-ID: <20050131093509FD%kamada@nanohz.org>)


#10 [**] Kerberos allows variable length checksum (section 5)
(solution proposed)

	I'd have to go back and check, but I don't think we require that 
	a given checksum type have a fixed output size, so "leave X amount of 
	space and fill it with zero for computing the checksum" is questionable 
	too.  (Ken Raeburn)

	Proposed solution: look at #9


#11 [*] Kerberos checksum is not deterministic (section 5)
(solution proposed)

	The Kink description of how to verify a checksum assumes that
	Kerberos checksums are deterministic; this is not strictly required.
	(Sam Hartman)

	let kcrypto specify how 
	to verify a checksum, as they're not required to be deterministic, so 
	the "compute it again and compare" approach specified in section 5 is 
	wrong  (Ken Raeburn)

	Proposed solution: look at #9


#12 [**] Subsession keys (section 5 and 8)

	Are subsession keys ignored?  (Ken Raeburn)

	The description of the checksum says that the session key of the
	ticket is used.  That's a way to do it, but the working group should
	explain why it has chosen to ignore the subsession key.
	(Sam Hartman)


#13 [**] Replay protection (section 5)

	The document claims that the transaction id is not used for
	replay detection because Kerberos provides that.  How is that true?
	The authenticator is protected against replays but how is the rest of
	the message bound to that specific authenticator instead of to a
	session key of a ticket?
	(Sam Hartman)


#14 [-] Reserved (15 bits) --  Reserved and must be zero (section 5)

	must be zero on send, must be ignored by receiver.


#15 [**] Principal name of KINK service (section 5.1.2)

	How do I discover the FQDN of my remote peer?   SPD
	entries are configured in terms of  IP addresses.  If you  want to
	store an identity in the PAD, why not store a principal instead of a
	hostname.


#16 [*] EPOCH (section 5.1.2)

	Perhaps you need a description of the time stamp?  I recall there
	being such a description in draft-housley-binarytime-xx.
	(Sam Hartman)

	The text is describing a 4-octet field in the KINK message header
	instead of ASN.1 field, so the description is not so needless.


#17 [**] Checksum when KRB-ERROR occured (section 5.1.4 and 7.1)

	Section 7.1 says the checksum in the KRB-ERROR message is not used,
	but section 5.1.4 says that KINK implementation MUST make use of
	keyed Kerberos errors.  But KRB-ERROR does not have checksum in it (at
	least with RFC 1510 or kerberos-clarifications).
	I think a correct phrase here is "KINK implementations MUST make use of
	a KINK Cksum field when returning KINK_KRB_ERROR and the appropriate
	service key is available."

	Remove following paragraph from section 5.1.4.  (Sam Hartman)
	  KINK implementations MUST make use of keyed Kerberos errors when  the
	  appropriate  service  key  is available as specified in [KRBREVS]. In
	  particular, clock  skew  errors  MUST  be  integrity  protected.  For
	  unauthenticated  Kerberos  errors,  the receiver MAY choose to act on
	  them, but SHOULD take precautions against make-work kinds of attacks.

	Drop reference to krb-error checksum from section 7.1.  (Sam Hartman)
	  defined in the following sections.  The checksum in the KRB-ERROR
	  message is not used, since the KINK header already contains a check-
	  sum field.


#18 [**] Kerberos error type limitations (section 5.1.4)

	Why should a sender send only those errors?  I'm mostly asking
	for an explanation to be given to me or to be added to the document
	rather than liberalization of the requirement.  (Sam Hartman)


#19 [**] Cross-realm and U2U (section 5.1.5)

	Please Consider how this works in the cross-realm case.
	I.E. make sure you end up with the right ticket on the right side.  I
	believe this text assumes that you need a ticket in a realm close to
	the client; I think that for things to work you actually need a realm
	close to the server.  Work through the message flows and make sure the
	KDC doing the decryption actually has the necessary keys and then
	adjust the document if necessary so the right KDC is used.

	The document needs to clearly indicate what error code is used in the
	case when the responder cannot get a ticket because some cross-realm
	key is missing.  In general we want it to be possible for an initiator
	to try several identities until the initiator finds the right one that
	has a shared key.  (Sam Hartman)


#20 [**] KINK_ENCRYPT format (section 5.1.8)

	The format of the encrypted part of KINK_ENCRYPT (section 5.1.8) is
	vague.  I think of using the output of raw encryption algorithms
	(i.e. E(confounder | plaintext | pad)) or using EncryptedData.

	treat "encryption with 
	integrity protection" output as a whole, don't peek under the covers to 
	find a "checksum" part you can throw away  (Ken Raeburn)

	drop references to the initialization vector  (Ken Raeburn)

	Please use the output of the kcrypto encrypt
	operation directly.  Of most importance is to make sure that all
	kcrypto enctypes will work even if it is not possible to decompose the
	kcrypto checksum from the encrypted data.  This probably means that in
	some cases you will have double checksums.
	You also need to deal with making sure you can determine the length of
	the plaintext.  (Sam Hartman)


#21 [*] Next Payload in KINK_ENCRYPT (section 5.1.8)

	Text should probably indacte that next payload must be none.


#22 [*] Kerberos PFS (section 6.8)

	Sec 6.8: "Kerberos in general does not provide FPS so it is somewhat 
	questionable whether a system which is heavily relying on Kerberos 
	benefits from PFS."  First, that sounds like it might be Security 
	Considerations material.  Second, I don't follow; explain please?
	(Ken Raeburn)


#23 [*] KE interoperability (section 6.8)

	What happens if a peer that implements the KE payloads communicates
	with a peer that does not.  Specify the behavior in sufficient detail
	to guarantee interoperability.  (Sam Hartman)


#24 [*] MUST/SHOULD in clock skew (section 7.1)

	The time difference MUST be computed and SHOULD be stored 
	and used?  Why the different requirement levels?  (And is this sort of 
	thing in the domain of KINK or Kerberos?)  (Ken Raeburn)


#25 [**] prf (section 8)

	Section 8 says "prf is the same hash algorithm found in the session
	ticket's etype", but krb-wg-crypto-07 defines hash as unkeyed.
	Fortunately krb-wg-crypto-07 defines a PRF for each etype, so KINK
	should use this PRF.

	Use a prf 
	from kcrypto, don't assume the checksum operations are deterministic 
	hash functions  (Ken Raeburn)

	Section 6.1 (the description of hash algorithm):
	This checksum may not be deterministic and is probably not
	appropriate for use in setting up a key.  A PRF is provided, although
	depending on how the hash is used the PRF may or may not be a suitable
	replacement.  There has been significant discussion within krb-wg on
	when the PRF is appropriate and when it is not.  This discussion
	centered around key determination in pkinit.  (Sam Hartman)


#26 [*] Key derivation (section 8)

	The key derivation seems inconsistent with the crypto framework
	document.  (Sam Hartman)

	I don't understand what this section says well enough to determine
	whether it works with kcrypto.  (Sam Hartman)


#27 [*](2401bis) SPD Considerations (section 10.1)

	This should not go in the security considartions section.  It is
	really more about IPsec architectural considerations than security
	considerations.

	This text needs to take into account 2401bis.  In particular it needs
	to be properly split between SPD considerations and PAD
	considerations.  (Sam Hartman)


#28 [*] Key usage

	Usage of  kink should specify the key usage numbers for kerberos
	encryption.  (Sam Hartman)


#29 [*](2401bis) Rekeying

	section 4.4.1:
	Please make sure this discussion is aligned with 2401bis.  I think it
	may change small details but they seem to have adopted much of the
	same strategy kink uses.  The area wher I believe they speak to this
	issue is when you should rekey (timers etc)


#30 [*](2401bis) IKEv2

	Should we adopt IKEv2?

	If we should...
	- IKEv2 does not have DOI, so how to handle the DOI field in the KINK
	  packet header should be described.
	- Use TS (Traffic Selector) instead of ID (Identification).
	- KEYMAT calculation is changed.
	- How to handle REKEY_SA Notify type.


#31 [*] behavior on KINK_ERROR

	In implementor's point of view, I'd like to see initiator's
	behavior in receiving KINK_ERROR to be defined.
	For example:
	- When KINK_OK is received, initiator MAY act as if the KINK_ERROR
	  payload was not included in the messaged.
	- When KINK_BADQMVERS is received and the Cksum is verified,
	  initiator MAY retry in other Quick Mode version.
	- When one of other error codes is received and the Cksum is verified,
	  initiator SHOULD abort the negotiation.


#32 [-] I-D nits

	Review the I-D nits and RFC authors docs.  I spotted a lot of 
	mechanical things (number of lines per page; avoid hyphenation; use 
	ragged right margin; need two spaces after sentence-ending period; fix 
	page numbers in table of contents; add section numbers to TOC) most of 
	which I think are specified in one of those documents.
	(Ken Raeburn)

	the document needs to meet all the ID nits when it is
	submitted.  (Sam Hartman)


#33 [-] IANA considerations (section 11)

	I think the correct terminology is "port 
	number", not "port", and they're "assigned", not "created".  This 
	section says no new registries are required in the first paragraph, and 
	the third one specifies that IANA must create one (but without the 
	associated procedural data that is required nowadays).  Are the KINK 
	payload types and ISAKMP payload types actually ever used in the same 
	field?  If not, I don't think they need to come out of the same 
	registry.  (Ken Raeburn)

	Needs work.  You may want to stop by tthe IANA office hours and ask
	them for advice.  They are generally quite good at working with
	authors to figure out how things need to be specified.
	(Sam Hartman)


#34 [-] Wording/Terminology

	Section 2 and 10.1.
	Kerberos is now using the term user-user rather than user-to-user.
	(Sam Hartman)

	Section 2.
	Principals are not either client or service principals;
	they can and often do fill both roles.  (Sam Hartman)

	Section 2, last paragraph.  "Between" is generally non-directional, 
	but in this case, a direction seems to be intended to be inferred; try 
	"from...to" instead.  (Ken Raeburn)

	Section 3, English usage/grammar problems with the first two paragraphs.
	(Sam Hartman)

	Section 3.
	   which allows a final acknowledgment message when the respondent needs
	   a full three-way handshake. This is only needed when the optimistic
	   keying route is not taken, though it is expected that that will not
	   be the norm. KINK also provides rekeying and dead peer detection as
	What is expected not to be the norm?  Please reword.
	(Sam Hartman)

	Section 4.3, discussing attributes, mixes singular and plural 
	indications.  The word "lone" appears to be popular with the author, 
	too. :-)  (Ken Raeburn)

	Sec 8: "By optional, it is meant..." is badly worded.  (Ken Raeburn)


#35 [-] References

	The reference to [PKCROSS] is unnecessary, and only happens once, in 
	the introduction.  I'd suggest dropping it.  That's one less 
	unpublished I-D in the references section.  (Ken Raeburn)

	[KRBREVS] is referenced but not listed in the references section.
	(Ken Raeburn)

	Sec 5.1.7, next to last paragraph on page 21, is "IKE" (the 
	protocol) fuzzy about use of different SAs, or is it "[IKE]" (the 
	document)?  (Ken Raeburn)

	Section 1:
	Remove the reference to pkcross or cite something outside the IETF.
	It's an expired ID without and active editor.  (Sam Hartman)

	Section 1:
	Add an informative reference to IKE.  (Sam Hartman)

	Section 2:
	Cite a reference for DER.  (Sam Hartman)

	Section 5: DOI
	Cite a specific registry please.  IANA registries are typically
	named, and a URL reference would probably be appropriate.


#36 [-] Typos

	4.4.2. Dead Peer Detection
	In the fourth paragraph, "loose" is to be "lose".

	5.1 KINK Payloads
	In the first item, the length of the Next Payload should be
	one octet instead of two.

	5.1.1. KINK Padding Rules
	In the second item, "other other" is to be "other".

	5.1.1. KINK Padding Rules
	The first item in the list should end with a period like 
	the others.  (Ken Raeburn)

	5.1.5. KINK_TGT_REQ Payload
	In the third item, "krbtgt/REALM/@REALM" is to be "krbtgt/REALM@REALM".

	5.1.6. KINK_TGT_REP Payload
	In the caption of Figure 13, "KINK_TGT_REQ" is to be "KINK_TGT_REP".

	7.3. CREATE
	"IPspec" is to be "IPsec".

	7.5. STATUS
	In the last paragraph, "REPLY KINK Header" should be in one line.
	In the last paragraph, "[KRB_ERROR]" is to be "[KINK_ERROR]".

	overall:
	"'s" is used in some places where I'd use "s" for a plural form.



-- 
KAMADA Ken'ichi <kamada@nanohz.org>



From owner-ietf-kink@mail.vpnc.org  Mon Jan 31 05:31:05 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10898
	for <kink-archive@lists.ietf.org>; Mon, 31 Jan 2005 05:31:04 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0VAPmuF017257;
	Mon, 31 Jan 2005 02:26:00 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j0VAPSP4017104;
	Mon, 31 Jan 2005 02:25:28 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from papa.tanu.org ([203.178.141.195])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j0VAOj5U016457
	for <ietf-kink@vpnc.org>; Mon, 31 Jan 2005 02:25:22 -0800 (PST)
	(envelope-from sakane@kame.net)
Received: from localhost (cp.64translator.com [202.214.123.2])
	by papa.tanu.org (8.12.9/8.12.8) with ESMTP id j0VANshB002857
	for <ietf-kink@vpnc.org>; Mon, 31 Jan 2005 19:23:56 +0900 (JST)
	(envelope-from sakane@kame.net)
To: ietf-kink@vpnc.org
Subject: Re: racoon2 release
In-Reply-To: Your message of "Fri, 28 Jan 2005 01:57:13 -0500"
	<6199f4b3455738c33a45787a74a5cf9e@mit.edu>
References: <6199f4b3455738c33a45787a74a5cf9e@mit.edu>
X-Mailer: Cue version 0.8 (041108-2350/sakane)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Message-Id: <20050131192331B.sakane@kame.net>
Date: Mon, 31 Jan 2005 19:23:31 +0900
From: Shoichi Sakane <sakane@kame.net>
X-Dispatcher: imput version 20030322(IM144)
Lines: 26
X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c
	on papa.tanu.org
X-Virus-Status: Clean
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


Hi, Ken.

You are right.  I only sent the README in the release to the racoon2
mailing list.  it described the draft version kink-06, but it did not
describe our plan related to developing KINK daemon.  i will add it
to the next release.  thank you.

> On Jan 27, 2005, at 22:40, Shoichi Sakane wrote:
> > We have removed our IKEv2 code from the release because we have an IPR
> > issue related to IKEv2.  We will release it after the issue will
> > be solved.  KINK is only supported in the release currently.
> 
> I may be being overly picky, but: KINK isn't finalized.  KINK would 
> presumably be the name of the final version of the protocol.  So it 
> wouldn't be correct to say that it supports KINK, but instead you 
> should indicate that it supports a specific draft.  And I expect that 
> the final version will not be 100% compatible with the current draft 
> (if only in the handling of some of the crypto aspects I've complained 
> about), so it would make sense to advise users of that fact as well, 
> and plan for either an incompatible change down the road, or support 
> for both draft and final versions in some future release.
> 
> That said, I think it's great that you're doing this.  Thank you!
> 
> Ken
> 



From owner-ietf-kink@mail.vpnc.org  Mon Jan 31 19:52:01 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01315
	for <kink-archive@lists.ietf.org>; Mon, 31 Jan 2005 19:51:58 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j110heLL038312;
	Mon, 31 Jan 2005 16:43:40 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j110he2L038311;
	Mon, 31 Jan 2005 16:43:40 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from sj-iport-2.cisco.com (sj-iport-2-in.cisco.com [171.71.176.71])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j110hevW038302
	for <ietf-kink@vpnc.org>; Mon, 31 Jan 2005 16:43:40 -0800 (PST)
	(envelope-from mat@cisco.com)
Received: from sj-core-1.cisco.com (171.71.177.237)
  by sj-iport-2.cisco.com with ESMTP; 31 Jan 2005 16:50:33 -0800
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j110hUM8001801;
	Mon, 31 Jan 2005 16:43:30 -0800 (PST)
Received: from thomasm-lnx.cisco.com (thomasm-lnx.cisco.com [171.71.96.50])
	by imail.cisco.com (8.12.11/8.12.10) with ESMTP id j110dIik002005;
	Mon, 31 Jan 2005 16:39:18 -0800
Subject: Re: Subsession keys (Re: KINK issue list)
From: Michael Thomas <mat@cisco.com>
To: "KAMADA Ken'ichi" <kamada@nanohz.org>
Cc: ietf-kink@vpnc.org
In-Reply-To: <20050127171703FZ%kamada@nanohz.org>
References: <20050120102450Q.sakane@kame.net>
	 <20050120103639RZ%kamada@nanohz.org> <20050120110448RR%kamada@nanohz.org>
	 <20050127171703FZ%kamada@nanohz.org>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-/29ectudUcUmHhj6yzeW"
Organization: Cisco Systems
Message-Id: <1107218609.31993.28.camel@thomasm-lnx.cisco.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 
Date: Mon, 31 Jan 2005 16:43:29 -0800
IIM-SIG: v:"1.1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs";
	t:"1107218358.313906"; x:"432200"; a:"rsa-sha1"; b:"nofws:968";
	e:"Iw=="; n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2p"
	"XIweAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRUtW+c43sl9jC"
	"50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc=";
	s:"AHwn12Sw8p4h910lDy/b9mSLKTPNkc+KZP47iKh6+XujlUnNygZq/AGp1fTP/VMWPffkvmqD"
	"GSx5rVHP3PNu4EwMF31ky+5jxUBwLIwITELK2IOtlt5y1AvDYtTF1d1RnY5YXNSP0qHPjHbbctl"
	"HLz7kqI3j8ZnjxFpo8AzgXpc=";
	c:"Subject: Re: Subsession keys (Re: KINK issue list)";
	c:"From: Michael Thomas <mat@cisco.com>";
	c:"Date: Mon, 31 Jan 2005 16:43:29 -0800"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com";
	c:"message from imail.cisco.com verified; "
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>



--=-/29ectudUcUmHhj6yzeW
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Thu, 2005-01-27 at 00:17, KAMADA Ken'ichi wrote:
> At Thu, 20 Jan 2005 11:04:48 +0900,
> "KAMADA Ken'ichi" <kamada@nanohz.org> wrote:
> >=20
> > [*] Subsession keys (section 5 and 8)
> >=20
> > 	Are subsession keys ignored?  (Ken Raeburn)
>=20
> I think they should not be ignored.

I'm hopelessly behind here, but I don't think I saw
a response to this... why should they be taken into
account? We're already mixing in entropy from the kdc
and the ipsec peers. What is more entropy in the form
of subsession keys buying us? Or am I missing the point?

		Mike

--=-/29ectudUcUmHhj6yzeW
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iQCVAwUAQf7QsbMsDAj/Eq++AQJiJgP/RraKTMoSpaBaFr3CwUyGLXGhlQ7557nM
8diU3kAJ79hty3NlH9Xab/u/icCir/yy5PtsI1vmfgpuTyjohnNDbgdmOecqGEQS
wkx6LJ3a2wCD7FnxyPWXAoK/RfZiNea5BGbi83bX4BufLEBpoausdWH2nvXvPmgk
HBzm53JoAc8=
=8SGE
-----END PGP SIGNATURE-----

--=-/29ectudUcUmHhj6yzeW--



From owner-ietf-kink@mail.vpnc.org  Mon Jan 31 19:58:51 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01951
	for <kink-archive@lists.ietf.org>; Mon, 31 Jan 2005 19:58:51 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j110tChd038924;
	Mon, 31 Jan 2005 16:55:12 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j110tCcB038923;
	Mon, 31 Jan 2005 16:55:12 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from nwkea-mail-1.sun.com (nwkea-mail-1.sun.com [192.18.42.13])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j110tBAm038917
	for <ietf-kink@vpnc.org>; Mon, 31 Jan 2005 16:55:11 -0800 (PST)
	(envelope-from sommerfeld@sun.com)
Received: from eastmail1bur.East.Sun.COM ([129.148.9.49])
	by nwkea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id j110t1iI015546;
	Mon, 31 Jan 2005 16:55:01 -0800 (PST)
Received: from thunk (thunk.East.Sun.COM [129.148.174.66])
	by eastmail1bur.East.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,v2.2) with ESMTP id j110t0Qp010335;
	Mon, 31 Jan 2005 19:55:00 -0500 (EST)
Received: from thunk.east.sun.com (localhost [127.0.0.1])
	by thunk (8.13.3+Sun/8.13.3) with ESMTP id j110t0ob005051;
	Mon, 31 Jan 2005 19:55:00 -0500 (EST)
Received: (from sommerfeld@localhost)
	by thunk.east.sun.com (8.13.3+Sun/8.13.3/Submit) id j110t0ub005050;
	Mon, 31 Jan 2005 19:55:00 -0500 (EST)
X-Authentication-Warning: thunk.east.sun.com: sommerfeld set sender to sommerfeld@sun.com using -f
Subject: Re: Subsession keys (Re: KINK issue list)
From: Bill Sommerfeld <sommerfeld@sun.com>
To: Michael Thomas <mat@cisco.com>
Cc: "KAMADA Ken'ichi" <kamada@nanohz.org>, ietf-kink@vpnc.org
In-Reply-To: <1107218609.31993.28.camel@thomasm-lnx.cisco.com>
References: <20050120102450Q.sakane@kame.net>
	 <20050120103639RZ%kamada@nanohz.org> <20050120110448RR%kamada@nanohz.org>
	 <20050127171703FZ%kamada@nanohz.org>
	 <1107218609.31993.28.camel@thomasm-lnx.cisco.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 7bit
Message-Id: <1107219299.1705.360.camel@thunk>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6.325 
Date: Mon, 31 Jan 2005 19:54:59 -0500
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


On Mon, 2005-01-31 at 19:43, Michael Thomas wrote:

> I'm hopelessly behind here, but I don't think I saw
> a response to this... why should they be taken into
> account? We're already mixing in entropy from the kdc
> and the ipsec peers. What is more entropy in the form
> of subsession keys buying us? Or am I missing the point?

the kerberos session key tends to be pretty long-lived and will be the same
from authentication to authentication between the same set of peers until
the ticket expires.  subsession keys are different every time.  it's low cost
and gets cryptographers off your back.

but it's not really all that different from a per-exchange nonce.

							- Bill



From owner-ietf-kink@mail.vpnc.org  Mon Jan 31 20:52:35 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05978
	for <kink-archive@lists.ietf.org>; Mon, 31 Jan 2005 20:52:34 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j111fXgt041515;
	Mon, 31 Jan 2005 17:41:33 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j111fXGY041514;
	Mon, 31 Jan 2005 17:41:33 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from cz.mit.edu (CARTER-ZIMMERMAN.MIT.EDU [18.18.3.197])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j111fWKi041508
	for <ietf-kink@vpnc.org>; Mon, 31 Jan 2005 17:41:33 -0800 (PST)
	(envelope-from hartmans@mit.edu)
Received: by cz.mit.edu (Postfix, from userid 8042)
	id C27E8E0063; Mon, 31 Jan 2005 20:41:30 -0500 (EST)
To: Michael Thomas <mat@cisco.com>
Cc: "KAMADA Ken'ichi" <kamada@nanohz.org>, ietf-kink@vpnc.org
Subject: Re: Subsession keys (Re: KINK issue list)
References: <20050120102450Q.sakane@kame.net>
	<20050120103639RZ%kamada@nanohz.org>
	<20050120110448RR%kamada@nanohz.org>
	<20050127171703FZ%kamada@nanohz.org>
	<1107218609.31993.28.camel@thomasm-lnx.cisco.com>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Mon, 31 Jan 2005 20:41:30 -0500
In-Reply-To: <1107218609.31993.28.camel@thomasm-lnx.cisco.com> (Michael
 Thomas's message of "Mon, 31 Jan 2005 16:43:29 -0800")
Message-ID: <tsly8e92h11.fsf@cz.mit.edu>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


>>>>> "Michael" == Michael Thomas <mat@cisco.com> writes:

    Michael> On Thu, 2005-01-27 at 00:17, KAMADA Ken'ichi wrote:
    >> At Thu, 20 Jan 2005 11:04:48 +0900,
    >> "KAMADA Ken'ichi" <kamada@nanohz.org> wrote:
    >> > 
    >> > [*] Subsession keys (section 5 and 8)
    >> > 
    >> > Are subsession keys ignored?  (Ken Raeburn)
    >> 
    >> I think they should not be ignored.

    Michael> I'm hopelessly behind here, but I don't think I saw a
    Michael> response to this... why should they be taken into
    Michael> account? We're already mixing in entropy from the kdc and
    Michael> the ipsec peers. What is more entropy in the form of
    Michael> subsession keys buying us? Or am I missing the point?

What Bill said is one reason.

My reason for bringing up the issue is that you are behaving
differently than all other Kerberos applications.  Kerberos libraries
are actually flexible enough to do what your spec currently asks but
it requires implementers to specifically handle subkeys that way.

If you don't have a reason for being different then please be the same
as everyone else.  If you do have a reason, explain it and I'll be
happy.


--Sam



From owner-ietf-kink@mail.vpnc.org  Mon Jan 31 21:07:33 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07371
	for <kink-archive@lists.ietf.org>; Mon, 31 Jan 2005 21:07:33 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j111tprS042398;
	Mon, 31 Jan 2005 17:55:51 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j111tprO042397;
	Mon, 31 Jan 2005 17:55:51 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from miyazawa.org (usen-221x116x13x66.ap-US01.usen.ad.jp [221.116.13.66])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j111tox4042361
	for <ietf-kink@vpnc.org>; Mon, 31 Jan 2005 17:55:50 -0800 (PST)
	(envelope-from kazunori@miyazawa.org)
Received: from [IPv6:2001:200:103:2000:e8e0:f89c:4c65:a4ac] ([2001:200:103:2000:e8e0:f89c:4c65:a4ac])
  (AUTH: LOGIN kazunori, SSL: TLSv1/SSLv3,256bits,AES256-SHA)
  by miyazawa.org with esmtp; Tue, 01 Feb 2005 10:54:57 +0900
  id 00007DB3.41FEE172.00001E1B
Message-ID: <41FEE165.2030400@miyazawa.org>
Date: Tue, 01 Feb 2005 10:54:45 +0900
From: Kazunori Miyazawa <kazunori@miyazawa.org>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: ja, en-us, en
MIME-Version: 1.0
To: "KAMADA Ken'ichi" <kamada@nanohz.org>, ietf-kink@vpnc.org
Subject: Re: KINK issue list
References: <20050120102450Q.sakane@kame.net>	<20050120103639RZ%kamada@nanohz.org> <20050120110448RR%kamada@nanohz.org>
In-Reply-To: <20050120110448RR%kamada@nanohz.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>
Content-Transfer-Encoding: 7bit


Hello,

I have read the mails and I think these issues could be closed.

Kamada-san described the checksum calculation and verification in
this mail.
http://www.vpnc.org/ietf-kink/mail-archive/msg00336.html

If KINK adopts this, check sum length in KINK header will be two
octets because kcrypto specifies that the output of get_mic is
no longer than 65535 octets in the section 4.

BTW, if there are no strong reason, I like to move the check sum
field from the header to the end of message, because we could
be easy to access KINK_AP_REQ/REP payload and forget it after
verification.

KAMADA Ken'ichi wrote:
> Here is a merged version of KINK issues expressed till now.
> If I missed some of them you noted, please let me know.
> 
> 

<snip>

> 
> 
> [*] CksumLen (section 5)
> 
> 	Diagram indicates one octet for cksumlen, but the text (and 
> 	kcrypto specifications) say it should be two.
> 
> 
> [**] etype does not directly indicate checksum type (section 5)
> 
> 	a key's encryption type does not directly indicate 
> 	a checksum type, it indicates an encryption(-with-integrity-protection) 
> 	scheme, which does include a required-to-implement checksum type
> 	(Ken Raeburn)
> 
> 
> [**] Kerberos allows variable length checksum (section 5)
> 
> 	I'd have to go back and check, but I don't think we require that 
> 	a given checksum type have a fixed output size, so "leave X amount of 
> 	space and fill it with zero for computing the checksum" is questionable 
> 	too.  (Ken Raeburn)
> 
> 
> [*] Kerberos checksum is not deterministic (section 5)
> 
> 	The Kink description of how to verify a checksum assumes that
> 	Kerberos checksums are deterministic; this is not strictly required.
> 	(Sam Hartman)
> 
> 	let kcrypto specify how 
> 	to verify a checksum, as they're not required to be deterministic, so 
> 	the "compute it again and compare" approach specified in section 5 is 
> 	wrong  (Ken Raeburn)
> 
> 	The spec should describe how to verify checksum as follows.
> 
> 	To verify the checksum, the checksum is saved, and the
> 	checksum field is zeroed out.  The resulting message and the saved
> 	checksum are passed to the verification function.  If the verification
> 	fails, the message MUST be dropped.
> 
> 

--
Kazunori Miyazawa




From owner-ietf-kink@mail.vpnc.org  Mon Jan 31 21:11:02 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07518
	for <kink-archive@lists.ietf.org>; Mon, 31 Jan 2005 21:11:01 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j111w6mS042491;
	Mon, 31 Jan 2005 17:58:06 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j111w6fm042490;
	Mon, 31 Jan 2005 17:58:06 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from nasten.nanohz.org (usen-220x218x5x242.ap-US00.usen.ad.jp [220.218.5.242])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j111w699042477
	for <ietf-kink@vpnc.org>; Mon, 31 Jan 2005 17:58:06 -0800 (PST)
	(envelope-from kamada@nanohz.org)
Received: from nasten.nanohz.org (localhost [127.0.0.1])
	by nasten.nanohz.org (Postfix) with ESMTP id 99F205
	for <ietf-kink@vpnc.org>; Tue,  1 Feb 2005 10:57:56 +0900 (JST)
Received: from mitana.nanohz.org ([2001:240:2:0:202:8aff:fefa:bec0])
	by nasten.nanohz.org (smtpsugar 1.1) with ESMTPA
	id 1fwyrr; Tue,  1 Feb 2005 10:57:56 +0900 (JST)
Date: Tue, 01 Feb 2005 10:59:00 +0900
Message-ID: <20050201105900MJ%kamada@nanohz.org>
From: "KAMADA Ken'ichi" <kamada@nanohz.org>
To: ietf-kink@vpnc.org
Subject: Re: AD Review: draft-ietf-kink-kink [starting at section 5]
In-Reply-To: <20050129021939.1963F76C87@luminous.mit.edu>
References: <20050129021939.1963F76C87@luminous.mit.edu>
User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.3.50
 (i386-unknown-netbsdelf2.0G) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


issue #13 Replay protection (section 5)

At Fri, 28 Jan 2005 21:19:39 -0500 (EST),
Sam Hartman <hartmans-ietf@mit.edu> wrote:
> 
> [**] The document claims that the transaction id is not used for
> replay detection because Kerberos provides that.  How is that true?
> The authenticator is protected against replays but how is the rest of
> the message bound to that specific authenticator instead of to a
> session key of a ticket?

The KINK checksum do it.  It is calculated from the whole message
including the authenticator, so replaying a part of a old message
with a newly captured authenticator will not succeed.

Am I missing your point?

-- 
KAMADA Ken'ichi <kamada@nanohz.org>



From owner-ietf-kink@mail.vpnc.org  Mon Jan 31 22:06:00 2005
Received: from above.proper.com (above.proper.com [208.184.76.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12577
	for <kink-archive@lists.ietf.org>; Mon, 31 Jan 2005 22:06:00 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j112qv4H045940;
	Mon, 31 Jan 2005 18:52:57 -0800 (PST)
	(envelope-from owner-ietf-kink@mail.vpnc.org)
Received: (from majordom@localhost)
	by above.proper.com (8.12.11/8.12.9/Submit) id j112qvPx045939;
	Mon, 31 Jan 2005 18:52:57 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-kink@mail.vpnc.org using -f
Received: from nasten.nanohz.org (usen-220x218x5x242.ap-US00.usen.ad.jp [220.218.5.242])
	by above.proper.com (8.12.11/8.12.9) with ESMTP id j112quNr045933
	for <ietf-kink@vpnc.org>; Mon, 31 Jan 2005 18:52:57 -0800 (PST)
	(envelope-from kamada@nanohz.org)
Received: from nasten.nanohz.org (localhost [127.0.0.1])
	by nasten.nanohz.org (Postfix) with ESMTP id 8230E5
	for <ietf-kink@vpnc.org>; Tue,  1 Feb 2005 11:52:56 +0900 (JST)
Received: from mitana.nanohz.org ([2001:240:2:0:202:8aff:fefa:bec0])
	by nasten.nanohz.org (smtpsugar 1.1) with ESMTPA
	id 1M61Cm; Tue,  1 Feb 2005 11:52:56 +0900 (JST)
Date: Tue, 01 Feb 2005 11:54:00 +0900
Message-ID: <20050201115400MZ%kamada@nanohz.org>
From: "KAMADA Ken'ichi" <kamada@nanohz.org>
To: ietf-kink@vpnc.org
Subject: Re: AD review: draft-ietf-kink-kink [section 1-4]
In-Reply-To: <tslzmz65pzn.fsf@cz.mit.edu>
References: <tslzmz65pzn.fsf@cz.mit.edu>
User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.3.50
 (i386-unknown-netbsdelf2.0G) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: owner-ietf-kink@mail.vpnc.org
Precedence: bulk
List-Archive: <http://www.vpnc.org/ietf-kink/mail-archive/>
List-Unsubscribe: <mailto:ietf-kink-request@vpnc.org?body=unsubscribe>
List-ID: <ietf-kink.vpnc.org>


At Tue, 18 Jan 2005 17:31:08 -0500,
Sam Hartman <hartmans-ietf@mit.edu> wrote:
> 
> Section 4.3:
> 
> [**] I need explicit review from the IPsec reviewer of this section to
> make sure it is compatible with 2401bis.  IN addition, any differences
> between how this works and how IKE would set up the same SA need to be
> called out.  It is fine for there to be differences, but I want to
> make sure the working group explicitly decided the differences are a
> good thing.
> 
> I'm somewhat concerned that 4.3 is not specific enough to describe
> exactly what key gets set up.  I.E. I'm concerned it may not be
> detailed enough for interoperable implementations.

Section 4.3 describes the message flow and section 7.3 describes the
message structure.  Differences between KINK and IKE is described
in section 7.3 (and also in section 4.4.1, 5.1.7, and 6).
I think they are enough to be interoperable (at least regarding SA
setup).
Is your concern resolved if section 4 referes to section 7?

-- 
KAMADA Ken'ichi <kamada@nanohz.org>



