From hipsec-bounces@lists.ietf.org Thu Oct 06 01:59:57 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ENOnN-0004UM-Eb; Thu, 06 Oct 2005 01:59:57 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ENOnL-0004UE-Lh for hipsec@megatron.ietf.org; Thu, 06 Oct 2005 01:59:55 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA25914 for ; Thu, 6 Oct 2005 01:59:51 -0400 (EDT) Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENOwF-00063p-QQ for hipsec@ietf.org; Thu, 06 Oct 2005 02:09:13 -0400 Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 01C0F276; Thu, 6 Oct 2005 07:59:34 +0200 (CEST) Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Thu, 6 Oct 2005 07:58:32 +0200 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Thu, 6 Oct 2005 07:58:32 +0200 Received: from [131.160.36.106] (EGIUM000L5C5TEU.lmf.ericsson.se [131.160.36.106]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 581842501; Thu, 6 Oct 2005 08:58:32 +0300 (EEST) Message-ID: <4344BD08.3030501@ericsson.com> Date: Thu, 06 Oct 2005 08:58:32 +0300 From: Gonzalo Camarillo User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: HIP Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 06 Oct 2005 05:58:32.0863 (UTC) FILETIME=[FBA362F0:01C5CA3A] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: 08e48e05374109708c00c6208b534009 Content-Transfer-Encoding: 7bit Cc: David Ward Subject: [Hipsec] New milestones X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org Folks, FYI: the new milestones are finally available at the official IETF site: http://www.ietf.org/html.charters/hip-charter.html Cheers, Gonzalo _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Fri Oct 07 05:03:37 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ENo8f-0001An-4V; Fri, 07 Oct 2005 05:03:37 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ENo8d-0001A4-GD for hipsec@megatron.ietf.org; Fri, 07 Oct 2005 05:03:35 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05535 for ; Fri, 7 Oct 2005 05:03:32 -0400 (EDT) Received: from mx.laposte.net ([81.255.54.11]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENoHd-00042O-78 for hipsec@ietf.org; Fri, 07 Oct 2005 05:13:09 -0400 Received: from [192.168.1.105] (212.119.9.178) by mx.laposte.net (7.2.060.1) (authenticated as julien.laganier) id 42FA13AB02F963EE; Fri, 7 Oct 2005 10:57:36 +0200 From: Julien Laganier To: hipsec@ietf.org Subject: Re: [Hipsec] New milestones Date: Fri, 7 Oct 2005 10:59:06 +0200 User-Agent: KMail/1.8 References: <4344BD08.3030501@ericsson.com> In-Reply-To: <4344BD08.3030501@ericsson.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510071059.07027.julien.IETF@laposte.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be Content-Transfer-Encoding: 7bit Cc: HIP , David Ward X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org On Thursday 06 October 2005 07:58, Gonzalo Camarillo wrote: > Folks, > > FYI: the new milestones are finally available at the official IETF > site: http://www.ietf.org/html.charters/hip-charter.html Folks, Considering these milestones: Oct 05 WGLC the HIP registration extensions specification -------------------------------------------------------------- => I believe the current document is ready for WGLC. Oct 05 WG LC on the basic HIP rendezvous mechanism specification --------------------------------------------------------------------- => I believe the current document is ready, apart from the references in which I think we should remove RFC1498 'On the naming and binding of network destinations' and RFC3007 'Secure DNS Dynamic Update'. If nobody objects I will shortly resubmit a new version with these changes made, then we can proceed with WGLC. Oct 05 WGLC the HIP DNS resource record(s) specification ------------------------------------------------------------- => I believe the current document is nearly ready apart from minor details. If nobody objects, I will shortly resubmit a new version making the following change so that we can issue WGLC: o In the resolver queries examples of section 3 (Usage Scenarios), explain that implementation using IPs addrs in APIs will typically request A/AAAA RR first, while those using HIT in APIS will typically request HIPHI RR first. o HIPHI and HIPRVS RRs should be defined for all classes (like IPSECKEY RR) o The HIT algorithm is now defined by the KHI prefix. Hence we should remove the HIT algortithm field from the HIPHI RR. Then we need to make the HIT field mandatory in HIPHI RR. Hence a verifier would always known the prefix of the KHI/HIT, and so the hash method. This change need to be made because if SHA1 became insecure for generating KHIs, then we have to allocate another prefix for stronger KHIs. And if the HIPHI RR encodes neither of the Context ID nor hash method, then we would also be forced to define another RR to store the HIPHI information. o The HIPHI RR will have an explicit HIT length field; the current text seems to be confusing because it uses the encoding (which has a leading byte for the length of the string). I think it is better to use an explicit byte for length, followed by HIT. The HIPHI RR would then be changed from: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | HIT algorithm | PK algorithm | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ HIT | ~ ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | / / Public Key / / / +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-| To: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | PK algorithm | HIT length | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ HIT | ~ ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | / / Public Key / / / +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-| Thoughts, objections? --julien _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Fri Oct 07 05:09:30 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ENoEL-0002m3-TX; Fri, 07 Oct 2005 05:09:29 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ENoEJ-0002ls-Fv for hipsec@megatron.ietf.org; Fri, 07 Oct 2005 05:09:27 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05752 for ; Fri, 7 Oct 2005 05:09:25 -0400 (EDT) Received: from smtp0.netlab.nec.de ([195.37.70.40]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENoNY-0004JB-NR for hipsec@ietf.org; Fri, 07 Oct 2005 05:19:02 -0400 Received: from venus.office (europa.netlab.nec.de [10.1.1.25]) by smtp0.netlab.nec.de (Postfix) with ESMTP id 46518DC57; Fri, 7 Oct 2005 11:09:17 +0200 (CEST) Received: from n-eggert.office ([10.1.1.112]) by venus.office over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Fri, 7 Oct 2005 11:09:17 +0200 Received: from [127.0.0.1] (localhost [127.0.0.1]) by n-eggert.office (Postfix) with ESMTP id 06B3B319D67; Fri, 7 Oct 2005 11:09:17 +0200 (CEST) In-Reply-To: <200510071059.07027.julien.IETF@laposte.net> References: <4344BD08.3030501@ericsson.com> <200510071059.07027.julien.IETF@laposte.net> Mime-Version: 1.0 (Apple Message framework v734) Message-Id: <8943C996-D34C-44DF-993E-7DE081D69E49@netlab.nec.de> From: Lars Eggert Subject: Re: [Hipsec] New milestones Date: Fri, 7 Oct 2005 11:09:16 +0200 To: Julien Laganier X-Mailer: Apple Mail (2.734) X-OriginalArrivalTime: 07 Oct 2005 09:09:17.0158 (UTC) FILETIME=[CB61F860:01C5CB1E] X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f Cc: hipsec@ietf.org, David Ward X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1630580342==" Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org --===============1630580342== Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-25-45101507; protocol="application/pkcs7-signature" --Apple-Mail-25-45101507 Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-Transfer-Encoding: 7bit On Oct 7, 2005, at 10:59, Julien Laganier wrote: > Oct 05 WGLC the HIP registration extensions specification > -------------------------------------------------------------- > > => I believe the current document is ready for WGLC. I agree. > Oct 05 WG LC on the basic HIP rendezvous mechanism specification > --------------------------------------------------------------------- > > => I believe the current document is ready, apart from the references > in which I think we should remove RFC1498 'On the naming and binding > of network destinations' and RFC3007 'Secure DNS Dynamic Update'. If > nobody objects I will shortly resubmit a new version with these > changes made, then we can proceed with WGLC. Yup. These are not cited and probably left over from my original draft. (FYI, fenner's xml2rfc validator will find uncited references: http://rtg.ietf.org/~fenner/ietf/xml2rfc-valid/) Lars -- Lars Eggert NEC Network Laboratories --Apple-Mail-25-45101507 Content-Type: application/pkcs7-signature; name=smime.p7s Content-Disposition: attachment; filename=smime.p7s Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIKgzCCAyAw ggKJoAMCAQICAw9TWTANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt YWlsIElzc3VpbmcgQ0EwHhcNMDUwODE4MTAyOTU2WhcNMDYwODE4MTAyOTU2WjBgMQ8wDQYDVQQE EwZFZ2dlcnQxDTALBgNVBCoTBExhcnMxFDASBgNVBAMTC0xhcnMgRWdnZXJ0MSgwJgYJKoZIhvcN AQkBFhlsYXJzLmVnZ2VydEBuZXRsYWIubmVjLmRlMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB CgKCAQEA2gsuG8tAmM6U2ESsQjhcijJSq6oDG2c+KvvXJ/xcJXbSIOY8IInezIP0DP41H0gxwHNv AyOuwM6nh0r2wOhzdr77GlKXiij0LoFOpurScPKsC9KTykGAfZtAuCnWIRdDo67Urcw1e306yYgK xF1UzYwGamLalPjejQTRcjLPIbzM4c7fUN/sxmpkpzT2p6OCJDyPhBfSaZWtv3UEoKF+xssNYzOF DRCTHcLc3iXgF7z7J0ud8maUAadfb/25Gm7tJHzBOEonMPkHx2N8Ci0qNce0MMH/LVOVQlNO5kYJ vUJiT0du7LAo/hf8tq3luZrh/Cwc/313x6oKYVuHDBllrQIDAQABo2IwYDAqBgUrZQEEAQQhMB8C AQAwGjAYAgEEBBNMMnVNeWZmQk5VYk5KSmNkWjJzMCQGA1UdEQQdMBuBGWxhcnMuZWdnZXJ0QG5l dGxhYi5uZWMuZGUwDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQQFAAOBgQAovojiq8758E/78nMS vNvD4359F8XAICzWbhz6cXJaGzv1FJoQcV/RY1x6CQZDt9PqiPiqyQX+xLvqicmEURbGU5+aiWj2 usovQXd+Ts8Doj3tbjk35nD7Etc8a2+Y9fQRUS6spzgJr0fcq2FMYbDnOtf71Bn77KgckoUbIszu mTCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQI EwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1 bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMT G1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJl ZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNV BAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNU aGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAw gYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNa LIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUq VIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1Ud HwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVs Mi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYf qi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa 9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8wggQYMIIDgaADAgECAgEAMA0G CSqGSIb3DQEBBQUAMIG/MQswCQYDVQQGEwJERTEcMBoGA1UECBQTQmFkZW4tV8N1ZXJ0dGVtYmVy ZzETMBEGA1UEBxMKSGVpZGVsYmVyZzEXMBUGA1UEChMOTkVDIEV1cm9wZSBMdGQxHTAbBgNVBAsT FE5ldHdvcmsgTGFib3JhdG9yaWVzMRswGQYDVQQDExJrb2JlLm5ldGxhYi5uZWMuZGUxKDAmBgkq hkiG9w0BCQEWGWxhcnMuZWdnZXJ0QG5ldGxhYi5uZWMuZGUwHhcNMDQwNjE4MTE1MzA4WhcNMDkw NjE3MTE1MzA4WjCBvzELMAkGA1UEBhMCREUxHDAaBgNVBAgUE0JhZGVuLVfDdWVydHRlbWJlcmcx EzARBgNVBAcTCkhlaWRlbGJlcmcxFzAVBgNVBAoTDk5FQyBFdXJvcGUgTHRkMR0wGwYDVQQLExRO ZXR3b3JrIExhYm9yYXRvcmllczEbMBkGA1UEAxMSa29iZS5uZXRsYWIubmVjLmRlMSgwJgYJKoZI hvcNAQkBFhlsYXJzLmVnZ2VydEBuZXRsYWIubmVjLmRlMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCB iQKBgQC0OQwsE86Rrt0Zs0GOCsYmkGpPwcCFvVpOijIPv1dGolr5a8+7hXSAgRlUyoclq9xfhsUT wlU1qkvVRD3/QOfQyPUxQktxba2ksfsPAKUHovInWydC6rvLU89jtYGEdnRCyA+cEB/XcSADbd2z 9/XK4A2cxmMQiYpXIphYQAxIBwIDAQABo4IBIDCCARwwHQYDVR0OBBYEFOh7L9eqGHnAhbJdO4PY LYzxCaNNMIHsBgNVHSMEgeQwgeGAFOh7L9eqGHnAhbJdO4PYLYzxCaNNoYHFpIHCMIG/MQswCQYD VQQGEwJERTEcMBoGA1UECBQTQmFkZW4tV8N1ZXJ0dGVtYmVyZzETMBEGA1UEBxMKSGVpZGVsYmVy ZzEXMBUGA1UEChMOTkVDIEV1cm9wZSBMdGQxHTAbBgNVBAsTFE5ldHdvcmsgTGFib3JhdG9yaWVz MRswGQYDVQQDExJrb2JlLm5ldGxhYi5uZWMuZGUxKDAmBgkqhkiG9w0BCQEWGWxhcnMuZWdnZXJ0 QG5ldGxhYi5uZWMuZGWCAQAwDAYDVR0TBAUwAwEB/zANBgkqhkiG9w0BAQUFAAOBgQCX6Ipd3AF9 3FDzBaw3ZVvQzzCv/kGPBBzzrJ3n5u+4eQppmOifhuWHZfb8h8S++jqcoPHGVjjlP5PaFb+wL0NR piBalRclikD3xIY/hFoxJ1AHCO0AzfFxEflO10b4+smMrBYJtk5d9EAhr5hEgoGCM7QijBtnCwZB KLI9pFgW1zGCA6UwggOhAgEBMGkwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25z dWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1 aW5nIENBAgMPU1kwCQYFKw4DAhoFAKCCAhEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkq hkiG9w0BCQUxDxcNMDUxMDA3MDkwOTE3WjAjBgkqhkiG9w0BCQQxFgQUVY02RrpkPHHJxNGZkjno oqiY8OQwgdYGCSsGAQQBgjcQBDGByDCBxTCBvzELMAkGA1UEBhMCREUxHDAaBgNVBAgUE0JhZGVu LVfDdWVydHRlbWJlcmcxEzARBgNVBAcTCkhlaWRlbGJlcmcxFzAVBgNVBAoTDk5FQyBFdXJvcGUg THRkMR0wGwYDVQQLExROZXR3b3JrIExhYm9yYXRvcmllczEbMBkGA1UEAxMSa29iZS5uZXRsYWIu bmVjLmRlMSgwJgYJKoZIhvcNAQkBFhlsYXJzLmVnZ2VydEBuZXRsYWIubmVjLmRlAgEAMIHYBgsq hkiG9w0BCRACCzGByKCBxTCBvzELMAkGA1UEBhMCREUxHDAaBgNVBAgUE0JhZGVuLVfDdWVydHRl bWJlcmcxEzARBgNVBAcTCkhlaWRlbGJlcmcxFzAVBgNVBAoTDk5FQyBFdXJvcGUgTHRkMR0wGwYD VQQLExROZXR3b3JrIExhYm9yYXRvcmllczEbMBkGA1UEAxMSa29iZS5uZXRsYWIubmVjLmRlMSgw JgYJKoZIhvcNAQkBFhlsYXJzLmVnZ2VydEBuZXRsYWIubmVjLmRlAgEAMA0GCSqGSIb3DQEBAQUA BIIBAEiy1sZCiO0ES1igCG4lDolpTlmFZn+O4THRa/x93RrB7CuOO0sTWdE5smVj4Y5BtXm1fiZl zJn4XXd17+WQ+8nLpdXgzol4ifONagZi9pl3WT7t8sPOgImC/ITBnAWy/GMcIFmkXg74OTyfkTOL g8Y+ur1mxCPVRnroTpaacHJRxfQawG/KVl/KRFwzGCKsyKfnbaiCzvQE6+AVjJ0ivoz5TMYX4r3n QypRrLj1mol7kmozhg3G2buOLSTOI+CCLMMkDJcBtZpStSQtluAtDTlcO3LaKVj1ZVtIcW4k9926 MBqF6HlBd6aga11ivmJtac1XnwmZHDIbOu1AqIWrFK8AAAAAAAA= --Apple-Mail-25-45101507-- --===============1630580342== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec --===============1630580342==-- From hipsec-bounces@lists.ietf.org Fri Oct 07 05:27:29 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ENoVl-0007qk-6S; Fri, 07 Oct 2005 05:27:29 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ENoVk-0007qc-At for hipsec@megatron.ietf.org; Fri, 07 Oct 2005 05:27:28 -0400 Received: from mx.laposte.net (mx.laposte.net [81.255.54.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06311 for ; Fri, 7 Oct 2005 05:27:25 -0400 (EDT) Received: from [192.168.1.105] (212.119.9.178) by mx.laposte.net (7.2.060.1) (authenticated as julien.laganier) id 42FA13AB02F963EE; Fri, 7 Oct 2005 10:57:36 +0200 From: Julien Laganier To: hipsec@ietf.org Subject: Re: [Hipsec] New milestones Date: Fri, 7 Oct 2005 10:59:06 +0200 User-Agent: KMail/1.8 References: <4344BD08.3030501@ericsson.com> In-Reply-To: <4344BD08.3030501@ericsson.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510071059.07027.julien.IETF@laposte.net> Content-Transfer-Encoding: 7bit Cc: HIP , David Ward X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org On Thursday 06 October 2005 07:58, Gonzalo Camarillo wrote: > Folks, > > FYI: the new milestones are finally available at the official IETF > site: http://www.ietf.org/html.charters/hip-charter.html Folks, Considering these milestones: Oct 05 WGLC the HIP registration extensions specification -------------------------------------------------------------- => I believe the current document is ready for WGLC. Oct 05 WG LC on the basic HIP rendezvous mechanism specification --------------------------------------------------------------------- => I believe the current document is ready, apart from the references in which I think we should remove RFC1498 'On the naming and binding of network destinations' and RFC3007 'Secure DNS Dynamic Update'. If nobody objects I will shortly resubmit a new version with these changes made, then we can proceed with WGLC. Oct 05 WGLC the HIP DNS resource record(s) specification ------------------------------------------------------------- => I believe the current document is nearly ready apart from minor details. If nobody objects, I will shortly resubmit a new version making the following change so that we can issue WGLC: o In the resolver queries examples of section 3 (Usage Scenarios), explain that implementation using IPs addrs in APIs will typically request A/AAAA RR first, while those using HIT in APIS will typically request HIPHI RR first. o HIPHI and HIPRVS RRs should be defined for all classes (like IPSECKEY RR) o The HIT algorithm is now defined by the KHI prefix. Hence we should remove the HIT algortithm field from the HIPHI RR. Then we need to make the HIT field mandatory in HIPHI RR. Hence a verifier would always known the prefix of the KHI/HIT, and so the hash method. This change need to be made because if SHA1 became insecure for generating KHIs, then we have to allocate another prefix for stronger KHIs. And if the HIPHI RR encodes neither of the Context ID nor hash method, then we would also be forced to define another RR to store the HIPHI information. o The HIPHI RR will have an explicit HIT length field; the current text seems to be confusing because it uses the encoding (which has a leading byte for the length of the string). I think it is better to use an explicit byte for length, followed by HIT. The HIPHI RR would then be changed from: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | HIT algorithm | PK algorithm | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ HIT | ~ ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | / / Public Key / / / +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-| To: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | PK algorithm | HIT length | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ HIT | ~ ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | / / Public Key / / / +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-| Thoughts, objections? --julien _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Fri Oct 07 07:11:08 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ENq84-0004Cp-3D; Fri, 07 Oct 2005 07:11:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ENq82-0004Cb-Dc for hipsec@megatron.ietf.org; Fri, 07 Oct 2005 07:11:06 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11360 for ; Fri, 7 Oct 2005 07:11:03 -0400 (EDT) Received: from n2.nomadiclab.com ([193.234.219.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENqHI-0000e0-MS for hipsec@ietf.org; Fri, 07 Oct 2005 07:20:42 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) by n2.nomadiclab.com (Postfix) with ESMTP id 3BB5C212C46; Fri, 7 Oct 2005 14:10:46 +0300 (EEST) In-Reply-To: <200510071059.07027.julien.IETF@laposte.net> References: <4344BD08.3030501@ericsson.com> <200510071059.07027.julien.IETF@laposte.net> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <653382E3-D88B-4E03-AD73-498BEC9BB033@nomadiclab.com> Content-Transfer-Encoding: 7bit From: Pekka Nikander Subject: Re: [Hipsec] New milestones Date: Fri, 7 Oct 2005 13:10:44 +0200 To: Julien Laganier X-Mailer: Apple Mail (2.734) X-Spam-Score: 0.0 (/) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 Content-Transfer-Encoding: 7bit Cc: hipsec@ietf.org X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org > Oct 05 WGLC the HIP DNS resource record(s) specification > ------------------------------------------------------------- > > => I believe the current document is nearly ready apart from minor > details. If nobody objects, I will shortly resubmit a new version > making the following change so that we can issue WGLC: > > o In the resolver queries examples of section 3 (Usage Scenarios), > explain that implementation using IPs addrs in APIs will typically > request A/AAAA RR first, while those using HIT in APIS will typically > request HIPHI RR first. Sounds fine. > o HIPHI and HIPRVS RRs should be defined for all classes (like > IPSECKEY RR) Yes. > o The HIT algorithm is now defined by the KHI prefix. Hence we should > remove the HIT algortithm field from the HIPHI RR. Then we need to > make the HIT field mandatory in HIPHI RR. Hence a verifier would > always known the prefix of the KHI/HIT, and so the hash method. > > This change need to be made because if SHA1 became insecure for > generating KHIs, then we have to allocate another prefix for stronger > KHIs. And if the HIPHI RR encodes neither of the Context ID nor hash > method, then we would also be forced to define another RR to store > the HIPHI information. Right. > o The HIPHI RR will have an explicit HIT length field; the current > text seems to be confusing because it uses the > encoding (which has a leading byte for the length of the string). I > think it is better to use an explicit byte for length, followed by > HIT. Sounds good. Will the HIT be in plain binary then, i.e., 16 bytes for current HITs? --Pekka _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Fri Oct 07 07:54:53 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ENqoP-00061w-7E; Fri, 07 Oct 2005 07:54:53 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ENqoN-00061i-Ma for hipsec@megatron.ietf.org; Fri, 07 Oct 2005 07:54:51 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12904 for ; Fri, 7 Oct 2005 07:54:50 -0400 (EDT) Received: from mx.laposte.net ([81.255.54.11]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ENqxU-0002Kf-5H for hipsec@ietf.org; Fri, 07 Oct 2005 08:04:27 -0400 Received: from [192.168.1.105] (212.119.9.178) by mx.laposte.net (7.2.060.1) (authenticated as julien.laganier) id 431C638C012EE163; Fri, 7 Oct 2005 13:54:22 +0200 From: Julien Laganier To: Pekka Nikander Subject: Re: [Hipsec] New milestones Date: Fri, 7 Oct 2005 13:55:56 +0200 User-Agent: KMail/1.8 References: <4344BD08.3030501@ericsson.com> <200510071059.07027.julien.IETF@laposte.net> <653382E3-D88B-4E03-AD73-498BEC9BB033@nomadiclab.com> In-Reply-To: <653382E3-D88B-4E03-AD73-498BEC9BB033@nomadiclab.com> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200510071355.56988.julien.IETF@laposte.net> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Content-Transfer-Encoding: 7bit Cc: hipsec@ietf.org X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org On Friday 07 October 2005 13:10, Pekka Nikander wrote: > > > o The HIPHI RR will have an explicit HIT length field; the > > current text seems to be confusing because it uses the > string> encoding (which has a leading byte for the length of the > > string). I think it is better to use an explicit byte for length, > > followed by HIT. > > Sounds good. Will the HIT be in plain binary then, i.e., > 16 bytes for current HITs? Yes. Thanks. --julien _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Mon Oct 10 03:42:15 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EOsIZ-0004yd-5M; Mon, 10 Oct 2005 03:42:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EOsIX-0004yT-3k for hipsec@megatron.ietf.org; Mon, 10 Oct 2005 03:42:13 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22544 for ; Mon, 10 Oct 2005 03:42:11 -0400 (EDT) Received: from n2.nomadiclab.com ([193.234.219.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EOsSN-0004Kv-EJ for hipsec@ietf.org; Mon, 10 Oct 2005 03:52:24 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) by n2.nomadiclab.com (Postfix) with ESMTP id D4B46212C46 for ; Mon, 10 Oct 2005 10:41:42 +0300 (EEST) Mime-Version: 1.0 (Apple Message framework v734) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: hipsec@ietf.org From: Pekka Nikander Date: Mon, 10 Oct 2005 09:41:41 +0200 X-Mailer: Apple Mail (2.734) X-Spam-Score: 0.0 (/) X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4 Content-Transfer-Encoding: 7bit Cc: Subject: [Hipsec] SHIM6 adopting HIP packet format & small change to the format X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org In the SHIM6 interim meeting in Amsterdam, SHIM6 tentatively adopted the HIP packet format for the SHIM6 protocol proposal, with two little modifications in order to adopt the format better for SHIM6 purposes. This was a practical decision, with the intention of making it easier to create SHIM6/HIP hybrids for research purposes. Furthermore, the tentative decision does NOT mean that SHIM6 would, at this time, co-ordinate with HIP about packet type or parameter numbers, meaning that the HIP WG have to adopt to SHIM6 numbers if hybrid compatibility is needed. However, the aim is to keep the path open for perhaps adopting more from HIP to SHIM6 in some future date. The two tentative SHIM6 packet formats are as follows: PAYLOAD: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Next Header | 0 |1| Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Receiver Context Tag | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ CONTROL: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Next Header | Hdr Ext Len |0| Type |Type specific|0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Checksum | Type specific format | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type specific format | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The current HIP packet format is as follows: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Next Header | Header Length | Packet Type | VER. | RES. | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Controls | Checksum | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ In order to be compatible with SHIM6, we would need to do the following changes: - either - flip the places of RES. and VER. and make sure VER. is odd, or - take one bit from RES and make it one (I am adopting this) - make the first bit of Packet Type to be zero - flip the places of Checksum and Controls The resulting new HIP packet format would be as follows: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Next Header | Header Length |0| Packet Type | VER. | RES.|1| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Checksum | Controls | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ What do you think? Are we willing to do these changes? --Pekka _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Mon Oct 10 04:56:47 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EOtSh-00009T-F6; Mon, 10 Oct 2005 04:56:47 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EOtSf-00009O-En for hipsec@megatron.ietf.org; Mon, 10 Oct 2005 04:56:45 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25896 for ; Mon, 10 Oct 2005 04:56:43 -0400 (EDT) Received: from twilight.cs.hut.fi ([130.233.40.5]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EOtcW-0006Ng-Fy for hipsec@ietf.org; Mon, 10 Oct 2005 05:06:57 -0400 Received: by twilight.cs.hut.fi (Postfix, from userid 60001) id 2324A2D81; Mon, 10 Oct 2005 11:56:31 +0300 (EEST) X-Spam-Checker-Version: SpamAssassin 3.1.0-niksula20040914 (2005-09-13) on twilight.cs.hut.fi X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.1.0-niksula20040914 X-Spam-Niksula: No Received: from kekkonen.cs.hut.fi (kekkonen.cs.hut.fi [130.233.41.50]) by twilight.cs.hut.fi (Postfix) with ESMTP id B57262D77; Mon, 10 Oct 2005 11:56:30 +0300 (EEST) Received: (from mkomu@localhost) by kekkonen.cs.hut.fi (8.11.7p1+Sun/8.10.2) id j9A8uUx02395; Mon, 10 Oct 2005 11:56:30 +0300 (EEST) Date: Mon, 10 Oct 2005 11:56:30 +0300 (EEST) From: Miika Komu X-X-Sender: mkomu@kekkonen.cs.hut.fi To: Pekka Nikander Subject: Re: [Hipsec] SHIM6 adopting HIP packet format & small change to the format In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Cc: hipsec@ietf.org X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org On Mon, 10 Oct 2005, Pekka Nikander wrote: > In order to be compatible with SHIM6, we would need to do the following > changes: > > - either > - flip the places of RES. and VER. and make sure VER. is odd, or > - take one bit from RES and make it one (I am adopting this) > > - make the first bit of Packet Type to be zero > - flip the places of Checksum and Controls Was there some functional reason for the flips? I guess it is fine. -- Miika Komu miika@iki.fi http://www.iki.fi/miika/ _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Mon Oct 10 05:05:44 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EOtbM-0001UA-St; Mon, 10 Oct 2005 05:05:44 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EOtbL-0001U5-3s for hipsec@megatron.ietf.org; Mon, 10 Oct 2005 05:05:43 -0400 Received: from mx.laposte.net (mx.laposte.net [81.255.54.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26298 for ; Mon, 10 Oct 2005 05:05:40 -0400 (EDT) Received: from [192.168.1.105] (212.119.9.178) by mx.laposte.net (7.2.060.1) (authenticated as julien.laganier) id 42DE178C02DA7BFE; Mon, 10 Oct 2005 11:03:09 +0200 From: Julien Laganier To: hipsec@ietf.org Subject: Re: [Hipsec] SHIM6 adopting HIP packet format & small change to the format Date: Mon, 10 Oct 2005 11:04:45 +0200 User-Agent: KMail/1.8 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200510101104.45879.julien.IETF@laposte.net> Content-Transfer-Encoding: quoted-printable Cc: hipsec@ietf.org X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org On Monday 10 October 2005 09:41, Pekka Nikander wrote: > The resulting new HIP packet format would be as follows: 0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 1 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 2 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1=20 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Next Header =A0 | Header Length |0| Packet Type | =A0VER. | RES.|1| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | =A0 =A0 =A0 =A0 =A0 Checksum =A0 =A0 =A0 =A0 =A0 =A0| =A0 =A0 =A0 =A0 =A0= Controls =A0 =A0 =A0 =A0 =A0 =A0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > What do you think? =A0Are we willing to do these changes? I am fine with these changes. =2D-julien _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Mon Oct 10 05:06:19 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EOtbv-0001cn-7h; Mon, 10 Oct 2005 05:06:19 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EOtbr-0001cX-L2 for hipsec@megatron.ietf.org; Mon, 10 Oct 2005 05:06:15 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA26315 for ; Mon, 10 Oct 2005 05:06:13 -0400 (EDT) Received: from mx.laposte.net ([81.255.54.11]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EOtlU-0006Zj-5u for hipsec@ietf.org; Mon, 10 Oct 2005 05:16:28 -0400 Received: from [192.168.1.105] (212.119.9.178) by mx.laposte.net (7.2.060.1) (authenticated as julien.laganier) id 42DE178C02DA7BFE; Mon, 10 Oct 2005 11:03:09 +0200 From: Julien Laganier To: hipsec@ietf.org Subject: Re: [Hipsec] SHIM6 adopting HIP packet format & small change to the format Date: Mon, 10 Oct 2005 11:04:45 +0200 User-Agent: KMail/1.8 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200510101104.45879.julien.IETF@laposte.net> X-Spam-Score: 0.1 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: quoted-printable Cc: hipsec@ietf.org X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org On Monday 10 October 2005 09:41, Pekka Nikander wrote: > The resulting new HIP packet format would be as follows: 0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 1 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 2 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1=20 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Next Header =A0 | Header Length |0| Packet Type | =A0VER. | RES.|1| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | =A0 =A0 =A0 =A0 =A0 Checksum =A0 =A0 =A0 =A0 =A0 =A0| =A0 =A0 =A0 =A0 =A0= Controls =A0 =A0 =A0 =A0 =A0 =A0| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > What do you think? =A0Are we willing to do these changes? I am fine with these changes. =2D-julien _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Mon Oct 10 05:21:53 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EOtqz-00049z-63; Mon, 10 Oct 2005 05:21:53 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EOtqx-00049h-P8 for hipsec@megatron.ietf.org; Mon, 10 Oct 2005 05:21:51 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27275 for ; Mon, 10 Oct 2005 05:21:49 -0400 (EDT) Received: from n2.nomadiclab.com ([193.234.219.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EOu0p-00073I-2Y for hipsec@ietf.org; Mon, 10 Oct 2005 05:32:04 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) by n2.nomadiclab.com (Postfix) with ESMTP id ED084212DB8; Mon, 10 Oct 2005 12:21:30 +0300 (EEST) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <6E222B94-D1FD-4EA7-BD31-5789F6470DA6@nomadiclab.com> Content-Transfer-Encoding: 7bit From: Pekka Nikander Subject: Re: [Hipsec] SHIM6 adopting HIP packet format & small change to the format Date: Mon, 10 Oct 2005 11:21:29 +0200 To: Miika Komu X-Mailer: Apple Mail (2.734) X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Content-Transfer-Encoding: 7bit Cc: hipsec@ietf.org X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org >> In order to be compatible with SHIM6, we would need to do the >> following >> changes: >> >> - either >> - flip the places of RES. and VER. and make sure VER. is odd, or >> - take one bit from RES and make it one (I am adopting this) >> >> - make the first bit of Packet Type to be zero >> - flip the places of Checksum and Controls >> > > Was there some functional reason for the flips? I guess it is fine. The checksum and controls changed place so that SHIM6 packet type specific content can be continuous. --Pekka _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Mon Oct 10 15:50:09 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EP3ez-0005CH-8Y; Mon, 10 Oct 2005 15:50:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EP3et-00059p-0f; Mon, 10 Oct 2005 15:50:03 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17012; Mon, 10 Oct 2005 15:50:00 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EP3oq-0006dF-JK; Mon, 10 Oct 2005 16:00:21 -0400 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1EP3er-0002ML-Uq; Mon, 10 Oct 2005 15:50:01 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 10 Oct 2005 15:50:01 -0400 X-Spam-Score: 0.4 (/) X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be Cc: hipsec@ietf.org Subject: [Hipsec] I-D ACTION:draft-ietf-hip-dns-03.txt X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Host Identity Protocol Working Group of the IETF. Title : Host Identity Protocol (HIP) Domain Name System (DNS) Extensions Author(s) : P. Nikander, J. Laganier Filename : draft-ietf-hip-dns-03.txt Pages : 26 Date : 2005-10-10 This document specifies two new resource records (RRs) for the Domain Name System (DNS), and how to use them with the Host Identity Protocol (HIP). These RRs allow a HIP node to store in the DNS its Host Identity (HI, the public component of the node public-private key pair), Host Identity Tag (HIT, a truncated hash of its public key), and the Domain Name or IP addresses of its rendezvous servers (RVS). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hip-dns-03.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-hip-dns-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-hip-dns-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-10-10105541.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-hip-dns-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-hip-dns-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-10-10105541.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec --NextPart-- From hipsec-bounces@lists.ietf.org Mon Oct 10 15:50:27 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EP3fG-0005Id-TP; Mon, 10 Oct 2005 15:50:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EP3et-0005AV-OO; Mon, 10 Oct 2005 15:50:03 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17025; Mon, 10 Oct 2005 15:50:01 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EP3oq-0006dC-J1; Mon, 10 Oct 2005 16:00:21 -0400 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1EP3er-0002MD-T2; Mon, 10 Oct 2005 15:50:01 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 10 Oct 2005 15:50:01 -0400 X-Spam-Score: 0.4 (/) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: hipsec@ietf.org Subject: [Hipsec] I-D ACTION:draft-ietf-hip-rvs-04.txt X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Host Identity Protocol Working Group of the IETF. Title : Host Identity Protocol (HIP) Rendezvous Extension Author(s) : J. Laganier, L. Eggert Filename : draft-ietf-hip-rvs-04.txt Pages : 14 Date : 2005-10-10 This document defines a rendezvous extension for the Host Identity Protocol (HIP). The rendezvous extension extends HIP and the HIP registration extension for initiating communication between HIP nodes via HIP rendezvous servers. Rendezvous servers improve reachability and operation when HIP nodes are multi-homed or mobile. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hip-rvs-04.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-hip-rvs-04.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-hip-rvs-04.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-10-10104335.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-hip-rvs-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-hip-rvs-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-10-10104335.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec --NextPart-- From hipsec-bounces@lists.ietf.org Thu Oct 13 12:34:11 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EQ61z-0002lA-FX; Thu, 13 Oct 2005 12:34:11 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EQ61y-0002l5-9H for hipsec@megatron.ietf.org; Thu, 13 Oct 2005 12:34:10 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27545 for ; Thu, 13 Oct 2005 12:34:05 -0400 (EDT) Received: from blv-smtpout-01.boeing.com ([130.76.32.69]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EQ6CT-0000BW-1J for hipsec@ietf.org; Thu, 13 Oct 2005 12:45:04 -0400 Received: from blv-av-01.boeing.com ([192.42.227.216]) by blv-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id JAA00585; Thu, 13 Oct 2005 09:33:44 -0700 (PDT) Received: from XCH-NWBH-11.nw.nos.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id j9DGXhJ10255; Thu, 13 Oct 2005 09:33:44 -0700 (PDT) Received: from XCH-NW-5V1.nw.nos.boeing.com ([130.247.55.44]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 13 Oct 2005 09:33:39 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [Hipsec] SHIM6 adopting HIP packet format & small change to theformat Date: Thu, 13 Oct 2005 09:33:39 -0700 Message-ID: <77F357662F8BFA4CA7074B0410171B6DC9E391@XCH-NW-5V1.nw.nos.boeing.com> Thread-Topic: [Hipsec] SHIM6 adopting HIP packet format & small change to theformat Thread-Index: AcXNbnKNHUGLMc06SxGs+Z4NUxHfsACpNMGw From: "Henderson, Thomas R" To: "Pekka Nikander" , X-OriginalArrivalTime: 13 Oct 2005 16:33:39.0708 (UTC) FILETIME=[DDFABBC0:01C5D013] X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Content-Transfer-Encoding: quoted-printable Cc: X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org >=20 > What do you think? Are we willing to do these changes? >=20 I think this is a great opportunity for convergence. I support aligning HIP in this way, but I would like to know how stable the shim6 format is at this time. Tom _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Fri Oct 14 06:02:06 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EQMO6-0002V7-Om; Fri, 14 Oct 2005 06:02:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EQMO4-0002Tf-9J for hipsec@megatron.ietf.org; Fri, 14 Oct 2005 06:02:04 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29522 for ; Fri, 14 Oct 2005 06:01:59 -0400 (EDT) Received: from n2.nomadiclab.com ([193.234.219.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EQMYi-0006V0-4X for hipsec@ietf.org; Fri, 14 Oct 2005 06:13:07 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) by n2.nomadiclab.com (Postfix) with ESMTP id C1909212CE0; Fri, 14 Oct 2005 13:01:46 +0300 (EEST) In-Reply-To: <77F357662F8BFA4CA7074B0410171B6DC9E391@XCH-NW-5V1.nw.nos.boeing.com> References: <77F357662F8BFA4CA7074B0410171B6DC9E391@XCH-NW-5V1.nw.nos.boeing.com> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Pekka Nikander Subject: Re: [Hipsec] SHIM6 adopting HIP packet format & small change to theformat Date: Fri, 14 Oct 2005 12:01:44 +0200 To: "Henderson, Thomas R" X-Mailer: Apple Mail (2.734) X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Content-Transfer-Encoding: 7bit Cc: hipsec@ietf.org X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org >> What do you think? Are we willing to do these changes? > > I think this is a great opportunity for convergence. I support > aligning > HIP in this way, but I would like to know how stable the shim6 > format is > at this time. Impossible to say at this time. We'll know better after Vancouver. I have no idea how we are proceeding with the cross-area reviews. The changes (swapping the place of the checksum and controls and setting one reserved bit) are not that big, though. IMHO, we might take the risk, if needed. --Pekka _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Fri Oct 14 09:04:18 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EQPEQ-00083o-PR; Fri, 14 Oct 2005 09:04:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EQPEP-0007zR-8I for hipsec@megatron.ietf.org; Fri, 14 Oct 2005 09:04:17 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08390 for ; Fri, 14 Oct 2005 09:04:11 -0400 (EDT) Received: from n2.nomadiclab.com ([193.234.219.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EQPP7-0002cp-Q2 for hipsec@ietf.org; Fri, 14 Oct 2005 09:15:22 -0400 Received: from localhost (inside.nomadiclab.com [193.234.219.2]) by n2.nomadiclab.com (Postfix) with ESMTP id 1C2B5212CE0 for ; Fri, 14 Oct 2005 16:03:56 +0300 (EEST) From: Jan Mikael Melen To: hipsec@ietf.org Date: Fri, 14 Oct 2005 16:03:48 +0300 User-Agent: KMail/1.8 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200510141603.50626.Jan.Melen@nomadiclab.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 Content-Transfer-Encoding: quoted-printable Cc: Subject: [Hipsec] BEET fall-back mode problem X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org Hi, One problem was discovered while implementing the BEET mode for Linux. The= =20 problem exists in the fall-back to tunnel mode when v4 options are present = in=20 the inner header. The current version of the draft says in section 5.5: 4. If there are any IPv4 header options in the original packet, it is RECOMMENDED that they are discarded. If the inner header contains an option that MUST be transported between the tunnel end-points, sender MAY encapsulate the inner header in to the ESP packet and set the ESP next header as IPv4 (4). Thus, sender MUST encapsulate the whole IP datagram similarly as in tunnel- mode. The inner header contains the BEET mode inner addresses as specified in the SA. This doesn't actually work because the resulting packet would be=20 indistinguishable from a normal IPIP tunnel packet that was encapsulated wi= th=20 BEET. The proposed solution would be that we reserve a pseudo-protocol (94) for t= he=20 BEET fall-back mode so that the NH of the ESP would point to this value whe= n=20 the fall-back mode is used. So the packet would look like: =A0 =A0 =A0 =A0 =A0 BEFORE APPLYING ESP =A0 =A0 =A0------------------------------- =A0 =A0 =A0| =A0inner IP hdr =A0| =A0 =A0 | =A0 =A0 =A0| =A0 =A0 =A0| (with options) | TCP | Data | =A0 =A0 =A0------------------------------- =A0 =A0 =A0 =A0 =A0 AFTER APPLYING ESP, OUTER v4 ADDRESSES =A0 =A0 =A0----------------------------------------------------------------= =2D-- =A0 =A0 =A0| outer IP hdr =A0| =A0 =A0 | =A0 =A0| orig IP | =A0 =A0 | =A0 = =A0 =A0| =A0 ESP =A0 | ESP | =A0 =A0 =A0| =A0 =A0 =A0 =A0 =A0 =A0 =A0 | ESP | PH | options | TCP | Data = | Trailer | ICV | =A0 =A0 =A0----------------------------------------------------------------= =2D-- =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0|<------------ encry= ption ----------->| =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0|<--------------- integrity ----= =2D---------->| Where PH is a 4-byte pseudo-header containing only the original NH (IP prot= o)=20 and the length of the original IP options. Protocol 94 is defined as a yet another IPIP tunneling protocol which is no= t=20 currently used for anything, just being a source of confusion for newbies := =2D)=20 Pekka has taken an action point to request the protocol number to be assign= ed=20 for BEET. Regards, Jan _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Fri Oct 14 13:23:48 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EQTHY-0007Ub-6f; Fri, 14 Oct 2005 13:23:48 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EQTHS-0007UH-UD for hipsec@megatron.ietf.org; Fri, 14 Oct 2005 13:23:43 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01710 for ; Fri, 14 Oct 2005 13:23:37 -0400 (EDT) Received: from p130.piuha.net ([193.234.218.130]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EQTSD-0004Xz-Mj for hipsec@ietf.org; Fri, 14 Oct 2005 13:34:50 -0400 Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id 02B7489815; Fri, 14 Oct 2005 20:23:32 +0300 (EEST) Message-ID: <434FE9A2.8030108@piuha.net> Date: Fri, 14 Oct 2005 20:23:46 +0300 From: Jari Arkko User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Julien Laganier , hipsec@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe Content-Transfer-Encoding: 7bit Cc: Subject: [Hipsec] review of draft-ietf-hip-registration-00.txt X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org Julien et al, I have read your draft. Overall, this draft is in VERY good shape for a -00 and probably ready for last call. I did have some comments, however: > In particular, REG_FAILED with a failure type of zero > indicates the service(s) type(s) that require further credentials for > registration. Hm. Are these "further credentials" defined somewhere? Would these be other certs, some userids (e.g. NAI) without security, or some additional authentication schemes, perhaps modelled after IKEv2's EAP mode? Also, I fear that this might lead us on a path where we start having a need to prove what was services were advertised, requested, and granted. Don't get me wrong, I would love this type of functionality. Just making a point that it may be harder than just "providing additional credentials". > 0 1 2 3 > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Type | Length | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Min Lifetime | Max Lifetime | Reg Type #1 | Reg Type #2 | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Reg Type #3 | | > +-+-+-+-+-+-+-+-+ Padding + > | | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Is there a provision for including parameters of some sort in the registration types. For instance, "I support RVS for the foobar domain". (Not sure if this is such a great example, but I'm pretty sure there will be services that go beyond "I do service X".) The same issue may appear for REG_REQUEST and REG_RESPONSE. This would complicate the packet, however. Editorial: > 0 1 2 3 > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Type | Length | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Min Lifetime | Max Lifetime | Reg Type #1 | Reg Type #2 | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > | Reg Type #3 | | > +-+-+-+-+-+-+-+-+ Padding + > | | > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ I think you mean Reg Type #1 ... Reg Type #n? --Jari _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Sun Oct 16 04:36:03 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ER3zu-0003Ke-Sz; Sun, 16 Oct 2005 04:36:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ER3zs-0003K5-I1 for hipsec@megatron.ietf.org; Sun, 16 Oct 2005 04:36:00 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18194 for ; Sun, 16 Oct 2005 04:35:53 -0400 (EDT) Received: from n2.nomadiclab.com ([193.234.219.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ER4Av-0004pH-Vj for hipsec@ietf.org; Sun, 16 Oct 2005 04:47:28 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) by n2.nomadiclab.com (Postfix) with ESMTP id B4B5C212DA6; Sun, 16 Oct 2005 11:35:23 +0300 (EEST) In-Reply-To: <434FE9A2.8030108@piuha.net> References: <434FE9A2.8030108@piuha.net> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <591E3B73-AE0C-4B5C-B523-99B9B02ED43D@nomadiclab.com> Content-Transfer-Encoding: 7bit From: Pekka Nikander Subject: Re: [Hipsec] review of draft-ietf-hip-registration-00.txt Date: Sun, 16 Oct 2005 10:35:21 +0200 To: Jari Arkko X-Mailer: Apple Mail (2.734) X-Spam-Score: 0.0 (/) X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2 Content-Transfer-Encoding: 7bit Cc: hipsec@ietf.org, Julien Laganier X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org Jari, Extensibility, or allowing new parameters to be attached to any given registration type in REG_INFO, REG_REQUEST, REG_RESPONSE, and REG_FAILED, was an explicit goal, IIRC. If the draft doesn't say that, such a statement should be added. A new subsection to Section 3 and something to Section 5, perhaps? (Unfortunately I don't have time now to propose text, sorry.) What comes to credentials, I think the best way forward is to explicitly say that establishing more credentials is beyond the scope of this spec and expected to be specified elsewhere. What do you think? --Pekka On Oct 14, 2005, at 19:23, Jari Arkko wrote: > > Julien et al, > > I have read your draft. Overall, this draft is in VERY good > shape for a -00 and probably ready for last call. I did have > some comments, however: > > >> In particular, REG_FAILED with a failure type of zero >> indicates the service(s) type(s) that require further credentials >> for >> registration. >> > > Hm. Are these "further credentials" defined somewhere? > Would these be other certs, some userids (e.g. NAI) without > security, or some additional authentication schemes, perhaps > modelled after IKEv2's EAP mode? > > Also, I fear that this might lead us on a path where we > start having a need to prove what was services were > advertised, requested, and granted. > > Don't get me wrong, I would love this type of functionality. > Just making a point that it may be harder than just "providing > additional credentials". > > >> 0 1 2 3 >> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | Type | Length | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | Min Lifetime | Max Lifetime | Reg Type #1 | Reg Type #2 | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | Reg Type #3 | | >> +-+-+-+-+-+-+-+-+ Padding + >> | | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> > > Is there a provision for including parameters of some sort in the > registration types. For instance, "I support RVS for the foobar > domain". > (Not sure if this is such a great example, but I'm pretty sure there > will be services that go beyond "I do service X".) The same issue > may appear for REG_REQUEST and REG_RESPONSE. > > This would complicate the packet, however. > > Editorial: > > >> 0 1 2 3 >> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | Type | Length | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | Min Lifetime | Max Lifetime | Reg Type #1 | Reg Type #2 | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> | Reg Type #3 | | >> +-+-+-+-+-+-+-+-+ Padding + >> | | >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> > > > I think you mean Reg Type #1 ... Reg Type #n? > > --Jari > > > _______________________________________________ > Hipsec mailing list > Hipsec@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/hipsec > > _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Sun Oct 16 04:40:52 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ER44a-0004aN-Hs; Sun, 16 Oct 2005 04:40:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ER44Y-0004aF-MY for hipsec@megatron.ietf.org; Sun, 16 Oct 2005 04:40:50 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18343 for ; Sun, 16 Oct 2005 04:40:44 -0400 (EDT) Received: from n2.nomadiclab.com ([193.234.219.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ER4Fe-0004u2-CQ for hipsec@ietf.org; Sun, 16 Oct 2005 04:52:18 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) by n2.nomadiclab.com (Postfix) with ESMTP id 3A4A7212DA6; Sun, 16 Oct 2005 11:40:41 +0300 (EEST) In-Reply-To: <200510141603.50626.Jan.Melen@nomadiclab.com> References: <200510141603.50626.Jan.Melen@nomadiclab.com> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Pekka Nikander Subject: Re: [Hipsec] BEET fall-back mode problem Date: Sun, 16 Oct 2005 10:40:40 +0200 To: Jan Mikael Melen X-Mailer: Apple Mail (2.734) X-Spam-Score: 2.0 (++) X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6 Content-Transfer-Encoding: 7bit Cc: hipsec@ietf.org X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org Small comments: I'd prefer the PH to be in the standard IPv6 extension header format, i.e., 8 bytes. Alternatively, might it be possible and useful to use GRE [RFC 2784] instead of defining a new extension? [I doubt, but just in case.] --Pekka On Oct 14, 2005, at 15:03, Jan Mikael Melen wrote: > Hi, > > One problem was discovered while implementing the BEET mode for > Linux. The > problem exists in the fall-back to tunnel mode when v4 options are > present in > the inner header. The current version of the draft says in section > 5.5: > 4. If there are any IPv4 header options in the original packet, it > is RECOMMENDED that they are discarded. If the inner header > contains an option that MUST be transported between the tunnel > end-points, sender MAY encapsulate the inner header in to > the ESP > packet and set the ESP next header as IPv4 (4). Thus, sender > MUST encapsulate the whole IP datagram similarly as in tunnel- > mode. The inner header contains the BEET mode inner > addresses as > specified in the SA. > > This doesn't actually work because the resulting packet would be > indistinguishable from a normal IPIP tunnel packet that was > encapsulated with > BEET. > > The proposed solution would be that we reserve a pseudo-protocol > (94) for the > BEET fall-back mode so that the NH of the ESP would point to this > value when > the fall-back mode is used. So the packet would look like: > > BEFORE APPLYING ESP > ------------------------------- > | inner IP hdr | | | > | (with options) | TCP | Data | > ------------------------------- > > AFTER APPLYING ESP, OUTER v4 ADDRESSES > > ------------------------------------------------------------------- > | outer IP hdr | | | orig IP | | | ESP | > ESP | > | | ESP | PH | options | TCP | Data | Trailer | > ICV | > > ------------------------------------------------------------------- > |<------------ encryption ----------->| > |<--------------- integrity --------------->| > > Where PH is a 4-byte pseudo-header containing only the original NH > (IP proto) > and the length of the original IP options. > > Protocol 94 is defined as a yet another IPIP tunneling protocol > which is not > currently used for anything, just being a source of confusion for > newbies :-) > Pekka has taken an action point to request the protocol number to > be assigned > for BEET. > > Regards, > Jan > > > _______________________________________________ > Hipsec mailing list > Hipsec@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/hipsec > > _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Sun Oct 16 05:38:40 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ER4yW-0002Lx-Lh; Sun, 16 Oct 2005 05:38:40 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ER4yV-0002Jk-2l for hipsec@megatron.ietf.org; Sun, 16 Oct 2005 05:38:39 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA22416 for ; Sun, 16 Oct 2005 05:38:31 -0400 (EDT) Received: from p130.piuha.net ([193.234.218.130]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ER59a-0006Fu-6S for hipsec@ietf.org; Sun, 16 Oct 2005 05:50:07 -0400 Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id 0B05F89815; Sun, 16 Oct 2005 12:38:17 +0300 (EEST) Message-ID: <43521F97.5030703@piuha.net> Date: Sun, 16 Oct 2005 12:38:31 +0300 From: Jari Arkko User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pekka Nikander Subject: Re: [Hipsec] review of draft-ietf-hip-registration-00.txt References: <434FE9A2.8030108@piuha.net> <591E3B73-AE0C-4B5C-B523-99B9B02ED43D@nomadiclab.com> In-Reply-To: <591E3B73-AE0C-4B5C-B523-99B9B02ED43D@nomadiclab.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Content-Transfer-Encoding: 7bit Cc: hipsec@ietf.org, Julien Laganier X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org Pekka, > Extensibility, or allowing new parameters to be attached > to any given registration type in REG_INFO, REG_REQUEST, > REG_RESPONSE, and REG_FAILED, was an explicit goal, IIRC. > If the draft doesn't say that, such a statement should > be added. A new subsection to Section 3 and something > to Section 5, perhaps? Works for me. And, of course, I may have missed a statement if it already was included there. > What comes to credentials, I think the best way forward > is to explicitly say that establishing more credentials > is beyond the scope of this spec and expected to be > specified elsewhere. What do you think? I think this is best. --Jari _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Mon Oct 17 04:29:41 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERQNJ-00024w-Jp; Mon, 17 Oct 2005 04:29:41 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERQNH-00024T-Po for hipsec@megatron.ietf.org; Mon, 17 Oct 2005 04:29:40 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24699 for ; Mon, 17 Oct 2005 04:29:32 -0400 (EDT) Received: from n2.nomadiclab.com ([193.234.219.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERQYY-0005CF-VB for hipsec@ietf.org; Mon, 17 Oct 2005 04:41:20 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) by n2.nomadiclab.com (Postfix) with ESMTP id 02692212DB9; Mon, 17 Oct 2005 11:29:18 +0300 (EEST) Message-ID: <435360DE.1010908@nomadiclab.com> Date: Mon, 17 Oct 2005 11:29:18 +0300 From: Petri Jokela User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pekka Nikander Subject: Re: [Hipsec] SHIM6 adopting HIP packet format & small change to theformat References: <77F357662F8BFA4CA7074B0410171B6DC9E391@XCH-NW-5V1.nw.nos.boeing.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Content-Transfer-Encoding: 7bit Cc: hipsec@ietf.org X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org Pekka Nikander wrote: >>> What do you think? Are we willing to do these changes? >> >> >> I think this is a great opportunity for convergence. I support aligning >> HIP in this way, but I would like to know how stable the shim6 format is >> at this time. > > Impossible to say at this time. We'll know better after Vancouver. > I have no idea how we are proceeding with the cross-area reviews. The request for a review has been sent to people mentioned earlier on the mailing list. Unfortunately we have received only one - and negative - response. > The changes (swapping the place of the checksum and controls and > setting one reserved bit) are not that big, though. IMHO, we might > take the risk, if needed. The checksum's place was selected so that it would be in the same location as UDP's checksum field. How possible it is that SHIM6 will change the checksum location in future drafts, maybe based on the same reason? Otherwise, the change looks ok. /petri _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Mon Oct 17 07:33:39 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERTFL-0004ym-3n; Mon, 17 Oct 2005 07:33:39 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERTFJ-0004y6-F7 for hipsec@megatron.ietf.org; Mon, 17 Oct 2005 07:33:37 -0400 Received: from mx.laposte.net (mx.laposte.net [81.255.54.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA05055 for ; Mon, 17 Oct 2005 07:33:24 -0400 (EDT) Received: from [192.168.1.105] (212.119.9.178) by mx.laposte.net (7.2.060.1) (authenticated as julien.laganier) id 431C605C0284A496; Mon, 17 Oct 2005 13:32:56 +0200 From: Julien Laganier To: Jari Arkko , Pekka Nikander Subject: Re: [Hipsec] review of draft-ietf-hip-registration-00.txt Date: Mon, 17 Oct 2005 13:34:39 +0200 User-Agent: KMail/1.8 References: <434FE9A2.8030108@piuha.net> <591E3B73-AE0C-4B5C-B523-99B9B02ED43D@nomadiclab.com> <43521F97.5030703@piuha.net> In-Reply-To: <43521F97.5030703@piuha.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510171334.39654.julien.IETF@laposte.net> Content-Transfer-Encoding: 7bit Cc: hipsec@ietf.org X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org On Sunday 16 October 2005 11:38, Jari Arkko wrote: > Pekka, > > > Extensibility, or allowing new parameters to be attached > > to any given registration type in REG_INFO, REG_REQUEST, > > REG_RESPONSE, and REG_FAILED, was an explicit goal, IIRC. > > If the draft doesn't say that, such a statement should > > be added. A new subsection to Section 3 and something > > to Section 5, perhaps? > > Works for me. And, of course, I may have missed a statement > if it already was included there. FWIW a previous version of the rendezvous I-D used that extensibility feature to allow registration with different flavors of the rendezvous service (i.e. header rewriting vs tunneling.) I went through the current registration I-D and this extensibility feature is mentionned in Section 5, "Establishing and Maintaining Registrations": Establishing and/or maintaining a registration may require additional information not available in the transmitted REG_REQUEST or REG_RESPONSE parameters. Therefore, registration type definitions MAY define dependencies for HIP parameters that are not defined in this document. Their semantics are subject to the specific registration type specifications. Is it sufficient, or should we add the following sentence in Section 3, "HIP Registration Extension Overview", between "...to register with the service." and "The following sections describe...": Both the registrar and the requester MAY also include in the messages exchanged additional HIP parameters specific to the registration type implicated. Other documents will define which and how these parameters shall be used. > > What comes to credentials, I think the best way forward > > is to explicitly say that establishing more credentials > > is beyond the scope of this spec and expected to be > > specified elsewhere. What do you think? > > I think this is best. Works for me. I suggest that we complete, in Section 3.3 "Registrar Granting or Refusing Service(s) Registration", the paragraphs: (...) In particular, REG_FAILED with a failure type of zero indicates the service(s) type(s) that require further credentials for registration. If the registrar requires further authorization and the requester has additional credentials available, the requester SHOULD try to again register with the service after the HIP association has been established. With the sentence: The precise means of establishing and verifying credentials are beyond the scope of this document and are expected to be defined in other documents. Thoughts? --julien _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Mon Oct 17 08:45:55 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERUNH-0005oS-RE; Mon, 17 Oct 2005 08:45:55 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERUNF-0005oJ-1Y for hipsec@megatron.ietf.org; Mon, 17 Oct 2005 08:45:53 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09816 for ; Mon, 17 Oct 2005 08:45:46 -0400 (EDT) Received: from kyoto.netlab.nec.de ([195.37.70.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERUYY-0004mS-Ei for hipsec@ietf.org; Mon, 17 Oct 2005 08:57:36 -0400 Received: from lars.local (p54AD1769.dip0.t-ipconnect.de [84.173.23.105]) by kyoto.netlab.nec.de (Postfix) with ESMTP id D35961BAC9E; Mon, 17 Oct 2005 14:45:41 +0200 (CEST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by lars.local (Postfix) with ESMTP id 33A0335AFD3; Mon, 17 Oct 2005 14:45:38 +0200 (CEST) In-Reply-To: <200510171334.39654.julien.IETF@laposte.net> References: <434FE9A2.8030108@piuha.net> <591E3B73-AE0C-4B5C-B523-99B9B02ED43D@nomadiclab.com> <43521F97.5030703@piuha.net> <200510171334.39654.julien.IETF@laposte.net> Mime-Version: 1.0 (Apple Message framework v734) Message-Id: <5478DDBA-F4E7-4EA8-8152-A1F67F53C2E6@netlab.nec.de> From: Lars Eggert Subject: Re: [Hipsec] review of draft-ietf-hip-registration-00.txt Date: Mon, 17 Oct 2005 14:45:33 +0200 To: Julien Laganier X-Mailer: Apple Mail (2.734) X-Spam-Score: 0.0 (/) X-Scan-Signature: f66b12316365a3fe519e75911daf28a8 Cc: hipsec@ietf.org X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1344794549==" Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org --===============1344794549== Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-16-922079150; protocol="application/pkcs7-signature" --Apple-Mail-16-922079150 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Both changes sound good to me. Lars PS: Thanks for the review, Jari! -- Lars Eggert NEC Network Laboratories --Apple-Mail-16-922079150 Content-Type: application/pkcs7-signature; name=smime.p7s Content-Disposition: attachment; filename=smime.p7s Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIKgzCCAyAw ggKJoAMCAQICAw9TWTANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt YWlsIElzc3VpbmcgQ0EwHhcNMDUwODE4MTAyOTU2WhcNMDYwODE4MTAyOTU2WjBgMQ8wDQYDVQQE EwZFZ2dlcnQxDTALBgNVBCoTBExhcnMxFDASBgNVBAMTC0xhcnMgRWdnZXJ0MSgwJgYJKoZIhvcN AQkBFhlsYXJzLmVnZ2VydEBuZXRsYWIubmVjLmRlMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB CgKCAQEA2gsuG8tAmM6U2ESsQjhcijJSq6oDG2c+KvvXJ/xcJXbSIOY8IInezIP0DP41H0gxwHNv AyOuwM6nh0r2wOhzdr77GlKXiij0LoFOpurScPKsC9KTykGAfZtAuCnWIRdDo67Urcw1e306yYgK xF1UzYwGamLalPjejQTRcjLPIbzM4c7fUN/sxmpkpzT2p6OCJDyPhBfSaZWtv3UEoKF+xssNYzOF DRCTHcLc3iXgF7z7J0ud8maUAadfb/25Gm7tJHzBOEonMPkHx2N8Ci0qNce0MMH/LVOVQlNO5kYJ vUJiT0du7LAo/hf8tq3luZrh/Cwc/313x6oKYVuHDBllrQIDAQABo2IwYDAqBgUrZQEEAQQhMB8C AQAwGjAYAgEEBBNMMnVNeWZmQk5VYk5KSmNkWjJzMCQGA1UdEQQdMBuBGWxhcnMuZWdnZXJ0QG5l dGxhYi5uZWMuZGUwDAYDVR0TAQH/BAIwADANBgkqhkiG9w0BAQQFAAOBgQAovojiq8758E/78nMS vNvD4359F8XAICzWbhz6cXJaGzv1FJoQcV/RY1x6CQZDt9PqiPiqyQX+xLvqicmEURbGU5+aiWj2 usovQXd+Ts8Doj3tbjk35nD7Etc8a2+Y9fQRUS6spzgJr0fcq2FMYbDnOtf71Bn77KgckoUbIszu mTCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEFBQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQI EwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1 bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMT G1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJl ZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNV BAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNU aGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAw gYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNa LIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUq VIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1Ud HwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWls Q0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVs Mi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYf qi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa 9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx0x1G/11fZU8wggQYMIIDgaADAgECAgEAMA0G CSqGSIb3DQEBBQUAMIG/MQswCQYDVQQGEwJERTEcMBoGA1UECBQTQmFkZW4tV8N1ZXJ0dGVtYmVy ZzETMBEGA1UEBxMKSGVpZGVsYmVyZzEXMBUGA1UEChMOTkVDIEV1cm9wZSBMdGQxHTAbBgNVBAsT FE5ldHdvcmsgTGFib3JhdG9yaWVzMRswGQYDVQQDExJrb2JlLm5ldGxhYi5uZWMuZGUxKDAmBgkq hkiG9w0BCQEWGWxhcnMuZWdnZXJ0QG5ldGxhYi5uZWMuZGUwHhcNMDQwNjE4MTE1MzA4WhcNMDkw NjE3MTE1MzA4WjCBvzELMAkGA1UEBhMCREUxHDAaBgNVBAgUE0JhZGVuLVfDdWVydHRlbWJlcmcx EzARBgNVBAcTCkhlaWRlbGJlcmcxFzAVBgNVBAoTDk5FQyBFdXJvcGUgTHRkMR0wGwYDVQQLExRO ZXR3b3JrIExhYm9yYXRvcmllczEbMBkGA1UEAxMSa29iZS5uZXRsYWIubmVjLmRlMSgwJgYJKoZI hvcNAQkBFhlsYXJzLmVnZ2VydEBuZXRsYWIubmVjLmRlMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCB iQKBgQC0OQwsE86Rrt0Zs0GOCsYmkGpPwcCFvVpOijIPv1dGolr5a8+7hXSAgRlUyoclq9xfhsUT wlU1qkvVRD3/QOfQyPUxQktxba2ksfsPAKUHovInWydC6rvLU89jtYGEdnRCyA+cEB/XcSADbd2z 9/XK4A2cxmMQiYpXIphYQAxIBwIDAQABo4IBIDCCARwwHQYDVR0OBBYEFOh7L9eqGHnAhbJdO4PY LYzxCaNNMIHsBgNVHSMEgeQwgeGAFOh7L9eqGHnAhbJdO4PYLYzxCaNNoYHFpIHCMIG/MQswCQYD VQQGEwJERTEcMBoGA1UECBQTQmFkZW4tV8N1ZXJ0dGVtYmVyZzETMBEGA1UEBxMKSGVpZGVsYmVy ZzEXMBUGA1UEChMOTkVDIEV1cm9wZSBMdGQxHTAbBgNVBAsTFE5ldHdvcmsgTGFib3JhdG9yaWVz MRswGQYDVQQDExJrb2JlLm5ldGxhYi5uZWMuZGUxKDAmBgkqhkiG9w0BCQEWGWxhcnMuZWdnZXJ0 QG5ldGxhYi5uZWMuZGWCAQAwDAYDVR0TBAUwAwEB/zANBgkqhkiG9w0BAQUFAAOBgQCX6Ipd3AF9 3FDzBaw3ZVvQzzCv/kGPBBzzrJ3n5u+4eQppmOifhuWHZfb8h8S++jqcoPHGVjjlP5PaFb+wL0NR piBalRclikD3xIY/hFoxJ1AHCO0AzfFxEflO10b4+smMrBYJtk5d9EAhr5hEgoGCM7QijBtnCwZB KLI9pFgW1zGCA6UwggOhAgEBMGkwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25z dWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1 aW5nIENBAgMPU1kwCQYFKw4DAhoFAKCCAhEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkq hkiG9w0BCQUxDxcNMDUxMDE3MTI0NTM0WjAjBgkqhkiG9w0BCQQxFgQUpp3gGIQC/0TO0309RGDJ DRCKFdcwgdYGCSsGAQQBgjcQBDGByDCBxTCBvzELMAkGA1UEBhMCREUxHDAaBgNVBAgUE0JhZGVu LVfDdWVydHRlbWJlcmcxEzARBgNVBAcTCkhlaWRlbGJlcmcxFzAVBgNVBAoTDk5FQyBFdXJvcGUg THRkMR0wGwYDVQQLExROZXR3b3JrIExhYm9yYXRvcmllczEbMBkGA1UEAxMSa29iZS5uZXRsYWIu bmVjLmRlMSgwJgYJKoZIhvcNAQkBFhlsYXJzLmVnZ2VydEBuZXRsYWIubmVjLmRlAgEAMIHYBgsq hkiG9w0BCRACCzGByKCBxTCBvzELMAkGA1UEBhMCREUxHDAaBgNVBAgUE0JhZGVuLVfDdWVydHRl bWJlcmcxEzARBgNVBAcTCkhlaWRlbGJlcmcxFzAVBgNVBAoTDk5FQyBFdXJvcGUgTHRkMR0wGwYD VQQLExROZXR3b3JrIExhYm9yYXRvcmllczEbMBkGA1UEAxMSa29iZS5uZXRsYWIubmVjLmRlMSgw JgYJKoZIhvcNAQkBFhlsYXJzLmVnZ2VydEBuZXRsYWIubmVjLmRlAgEAMA0GCSqGSIb3DQEBAQUA BIIBACcT7y1RQMlizfRNqlcq8Ie7kV0x+y9JgRIM896qY6XJD9CRD6/t65MiI6AL+M+1fWzDIpHe i8Aif2iH0gWY1WDGMKd4tXjLXngj6obpbe705A3AkEWSuSvZugq34LGXjf0hCl4A/eY/jLx3uW6y tMXDpja4O7Dw+F0cR6zn0ebs06Fzb3nQGUVAEbZy0rTu2uL8cMem06OLf/2ipPWGFpS4b+56ExTp g5sHxzIhot1G/GGASv0vW0BxBqeRRDDYH6oqVtu8QxhLBwHO7AKFjkzTXTj+rB7FNbL2G6jNM+ow onJkOsrmkKz/2DRJXsYzQUVp/DxGvHPwWG5ZPMAoV/8AAAAAAAA= --Apple-Mail-16-922079150-- --===============1344794549== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec --===============1344794549==-- From hipsec-bounces@lists.ietf.org Tue Oct 18 05:22:26 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERnfu-0002uB-EV; Tue, 18 Oct 2005 05:22:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERnfs-0002ty-FG for hipsec@megatron.ietf.org; Tue, 18 Oct 2005 05:22:24 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16038 for ; Tue, 18 Oct 2005 05:22:16 -0400 (EDT) Received: from n2.nomadiclab.com ([193.234.219.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERnrN-0006tb-02 for hipsec@ietf.org; Tue, 18 Oct 2005 05:34:18 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) by n2.nomadiclab.com (Postfix) with ESMTP id 2961B212C3D; Tue, 18 Oct 2005 12:22:14 +0300 (EEST) In-Reply-To: <435360DE.1010908@nomadiclab.com> References: <77F357662F8BFA4CA7074B0410171B6DC9E391@XCH-NW-5V1.nw.nos.boeing.com> <435360DE.1010908@nomadiclab.com> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <971F5700-F5FC-4500-AECF-A463DED58E11@nomadiclab.com> Content-Transfer-Encoding: 7bit From: Pekka Nikander Subject: Re: [Hipsec] SHIM6 adopting HIP packet format & small change to theformat Date: Tue, 18 Oct 2005 11:22:15 +0200 To: Petri Jokela X-Mailer: Apple Mail (2.734) X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: 7bit Cc: hipsec@ietf.org X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org >> The changes (swapping the place of the checksum and controls and >> setting one reserved bit) are not that big, though. IMHO, we might >> take the risk, if needed. > > The checksum's place was selected so that it would be in the same > location as UDP's checksum field. How possible it is that SHIM6 > will change the checksum location in future drafts, maybe based on > the same reason? I don't think SHIM6 will bother with that, since the issue is there anyway with existing IPv4 UDP only. From my point of view, it would be *nice* if we could use existing IPv4 UDP hardware to verify the checksum of the HIP header, but the potential ability to build hybrid shim6-HIP protocols is much more important. Hence, my vote is to give up the checksum compatibility with existing IPv4 UDP. --Pekka _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Tue Oct 18 07:42:22 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERprK-0007zg-OV; Tue, 18 Oct 2005 07:42:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERprI-0007z8-LZ for hipsec@megatron.ietf.org; Tue, 18 Oct 2005 07:42:21 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23596 for ; Tue, 18 Oct 2005 07:42:11 -0400 (EDT) Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERq2k-0002Gi-4R for hipsec@ietf.org; Tue, 18 Oct 2005 07:54:15 -0400 Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 0E502AB3; Tue, 18 Oct 2005 13:42:14 +0200 (CEST) Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Tue, 18 Oct 2005 13:41:44 +0200 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Tue, 18 Oct 2005 13:41:43 +0200 Received: from [131.160.126.56] (rvi2-126-56.lmf.ericsson.se [131.160.126.56]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 14C212760; Tue, 18 Oct 2005 14:41:42 +0300 (EEST) Message-ID: <4354DF75.9030306@ericsson.com> Date: Tue, 18 Oct 2005 14:41:41 +0300 From: Gonzalo Camarillo User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: HIP Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 18 Oct 2005 11:41:44.0022 (UTC) FILETIME=[E9E1E760:01C5D3D8] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Content-Transfer-Encoding: 7bit Cc: Pekka Nikander , Julien Laganier Subject: [Hipsec] WGLC draft-ietf-hip-dns-03.txt X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org Folks, we would like to working group last call the following draft. This working group last call will end on November 6th. http://www.ietf.org/internet-drafts/draft-ietf-hip-dns-03.txt Send your comments to this list. Thanks, Gonzalo HIP co-chair _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Tue Oct 18 07:44:14 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERpt7-0000Wa-W2; Tue, 18 Oct 2005 07:44:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERpt6-0000WP-FL for hipsec@megatron.ietf.org; Tue, 18 Oct 2005 07:44:12 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23714 for ; Tue, 18 Oct 2005 07:44:03 -0400 (EDT) Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERq4d-0002JI-6Q for hipsec@ietf.org; Tue, 18 Oct 2005 07:56:07 -0400 Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 28E5E746; Tue, 18 Oct 2005 13:44:11 +0200 (CEST) Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Tue, 18 Oct 2005 13:42:57 +0200 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Tue, 18 Oct 2005 13:42:57 +0200 Received: from [131.160.126.56] (rvi2-126-56.lmf.ericsson.se [131.160.126.56]) by mail.lmf.ericsson.se (Postfix) with ESMTP id AF33F2760; Tue, 18 Oct 2005 14:42:56 +0300 (EEST) Message-ID: <4354DFC0.2030103@ericsson.com> Date: Tue, 18 Oct 2005 14:42:56 +0300 From: Gonzalo Camarillo User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: HIP Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 18 Oct 2005 11:42:57.0726 (UTC) FILETIME=[15D03DE0:01C5D3D9] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Content-Transfer-Encoding: 7bit Cc: Lars Eggert , teemu.koponen@hiit.fi, Julien Laganier Subject: [Hipsec] WGLC draft-ietf-hip-registration-00.txt X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org Folks, we would like to working group last call the following draft. This working group last call will end on November 6th. http://www.ietf.org/internet-drafts/draft-ietf-hip-registration-00.txt Send your comments to this list. Note that Jari's comments on this draft will be taken as WGLC comments. Thanks, Gonzalo HIP co-chair _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Tue Oct 18 07:44:58 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERptq-0000a7-IN; Tue, 18 Oct 2005 07:44:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERptp-0000Zw-GG for hipsec@megatron.ietf.org; Tue, 18 Oct 2005 07:44:57 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23740 for ; Tue, 18 Oct 2005 07:44:48 -0400 (EDT) Received: from mailgw4.ericsson.se ([193.180.251.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERq5H-0002K9-3B for hipsec@ietf.org; Tue, 18 Oct 2005 07:56:52 -0400 Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 8EF8E54C; Tue, 18 Oct 2005 13:44:40 +0200 (CEST) Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Tue, 18 Oct 2005 13:42:11 +0200 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Tue, 18 Oct 2005 13:42:10 +0200 Received: from [131.160.126.56] (rvi2-126-56.lmf.ericsson.se [131.160.126.56]) by mail.lmf.ericsson.se (Postfix) with ESMTP id E28D62760; Tue, 18 Oct 2005 14:42:09 +0300 (EEST) Message-ID: <4354DF91.4010603@ericsson.com> Date: Tue, 18 Oct 2005 14:42:09 +0300 From: Gonzalo Camarillo User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: HIP Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 18 Oct 2005 11:42:10.0898 (UTC) FILETIME=[F9E6DB20:01C5D3D8] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Content-Transfer-Encoding: 7bit Cc: Lars Eggert , Julien Laganier Subject: [Hipsec] WGLC draft-ietf-hip-rvs-04.txt X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org Folks, we would like to working group last call the following draft. This working group last call will end on November 6th. http://www.ietf.org/internet-drafts/draft-ietf-hip-rvs-04.txt Send your comments to this list. Thanks, Gonzalo HIP co-chair _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Tue Oct 18 07:55:14 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERq3m-0003c5-BI; Tue, 18 Oct 2005 07:55:14 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERq3j-0003a8-NN for hipsec@megatron.ietf.org; Tue, 18 Oct 2005 07:55:12 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24305 for ; Tue, 18 Oct 2005 07:55:02 -0400 (EDT) Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERqFC-0002g1-7v for hipsec@ietf.org; Tue, 18 Oct 2005 08:07:06 -0400 Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 5918010BB; Tue, 18 Oct 2005 13:51:13 +0200 (CEST) Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Tue, 18 Oct 2005 13:50:26 +0200 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Tue, 18 Oct 2005 13:50:26 +0200 Received: from [131.160.126.56] (rvi2-126-56.lmf.ericsson.se [131.160.126.56]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 8F7082760; Tue, 18 Oct 2005 14:50:25 +0300 (EEST) Message-ID: <4354E181.7070105@ericsson.com> Date: Tue, 18 Oct 2005 14:50:25 +0300 From: Gonzalo Camarillo User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pekka Nikander Subject: Re: [Hipsec] SHIM6 adopting HIP packet format & small change to theformat References: <77F357662F8BFA4CA7074B0410171B6DC9E391@XCH-NW-5V1.nw.nos.boeing.com> <435360DE.1010908@nomadiclab.com> <971F5700-F5FC-4500-AECF-A463DED58E11@nomadiclab.com> In-Reply-To: <971F5700-F5FC-4500-AECF-A463DED58E11@nomadiclab.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 18 Oct 2005 11:50:26.0621 (UTC) FILETIME=[21602ED0:01C5D3DA] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 Content-Transfer-Encoding: 7bit Cc: hipsec@ietf.org, David Ward X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org Hi Pekka, is your proposal to perform this change in the current draft of the main HIP specification? Thanks, Gonzalo Pekka Nikander wrote: >>> The changes (swapping the place of the checksum and controls and >>> setting one reserved bit) are not that big, though. IMHO, we might >>> take the risk, if needed. >> >> >> The checksum's place was selected so that it would be in the same >> location as UDP's checksum field. How possible it is that SHIM6 will >> change the checksum location in future drafts, maybe based on the >> same reason? > > > I don't think SHIM6 will bother with that, since the issue is there > anyway with existing IPv4 UDP only. From my point of view, it would be > *nice* if we could use existing IPv4 UDP hardware to verify the > checksum of the HIP header, but the potential ability to build hybrid > shim6-HIP protocols is much more important. Hence, my vote is to give > up the checksum compatibility with existing IPv4 UDP. > > --Pekka > > > _______________________________________________ > Hipsec mailing list > Hipsec@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/hipsec > -- Gonzalo Camarillo Phone : +358 9 299 33 71 Oy L M Ericsson Ab Mobile: +358 40 702 35 35 Telecom R&D Fax : +358 9 299 30 52 FIN-02420 Jorvas Email : Gonzalo.Camarillo@ericsson.com Finland http://www.hut.fi/~gonzalo _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Tue Oct 18 08:05:52 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERqE4-0007AJ-Ld; Tue, 18 Oct 2005 08:05:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERqE3-0007A0-I7 for hipsec@megatron.ietf.org; Tue, 18 Oct 2005 08:05:51 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25337 for ; Tue, 18 Oct 2005 08:05:42 -0400 (EDT) Received: from n2.nomadiclab.com ([193.234.219.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERqPX-000343-Gz for hipsec@ietf.org; Tue, 18 Oct 2005 08:17:46 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) by n2.nomadiclab.com (Postfix) with ESMTP id 29E1D212C3D; Tue, 18 Oct 2005 15:05:34 +0300 (EEST) Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <02215F9C-9164-4632-9C88-85F607A2A0EA@nomadiclab.com> Content-Transfer-Encoding: 7bit From: Pekka Nikander Date: Tue, 18 Oct 2005 14:05:35 +0200 To: Gonzalo Camarillo , David Ward X-Mailer: Apple Mail (2.734) X-Spam-Score: 0.0 (/) X-Scan-Signature: 08e48e05374109708c00c6208b534009 Content-Transfer-Encoding: 7bit Cc: hipsec@ietf.org Subject: [Hipsec] Start re-chartering discussion in Vancouver? X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org Dear HIP WG chairs, Should we start HIP WG re-chartering discussion in Vancouver, with the intention of having a new charter proposal available before the Dallas meeting? --Pekka _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Tue Oct 18 08:29:28 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERqau-0007Ds-AJ; Tue, 18 Oct 2005 08:29:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ERqat-0007DJ-8y for hipsec@megatron.ietf.org; Tue, 18 Oct 2005 08:29:27 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26550 for ; Tue, 18 Oct 2005 08:29:17 -0400 (EDT) Received: from n2.nomadiclab.com ([193.234.219.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ERqmO-0003dU-TR for hipsec@ietf.org; Tue, 18 Oct 2005 08:41:22 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) by n2.nomadiclab.com (Postfix) with ESMTP id 4468D212C3D; Tue, 18 Oct 2005 15:29:16 +0300 (EEST) In-Reply-To: <4354E181.7070105@ericsson.com> References: <77F357662F8BFA4CA7074B0410171B6DC9E391@XCH-NW-5V1.nw.nos.boeing.com> <435360DE.1010908@nomadiclab.com> <971F5700-F5FC-4500-AECF-A463DED58E11@nomadiclab.com> <4354E181.7070105@ericsson.com> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Pekka Nikander Subject: Re: [Hipsec] SHIM6 adopting HIP packet format & small change to theformat Date: Tue, 18 Oct 2005 14:29:15 +0200 To: Gonzalo Camarillo X-Mailer: Apple Mail (2.734) X-Spam-Score: 0.0 (/) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca Content-Transfer-Encoding: 7bit Cc: hipsec@ietf.org, David Ward X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org Yes. Plus the other small changes that I described in my previous mail, right fresh out from SHIM6 interim. --Pekka On Oct 18, 2005, at 13:50, Gonzalo Camarillo wrote: > Hi Pekka, > > is your proposal to perform this change in the current draft of the > main HIP specification? > > Thanks, > > Gonzalo > > Pekka Nikander wrote: > >>>> The changes (swapping the place of the checksum and controls and >>>> setting one reserved bit) are not that big, though. IMHO, we might >>>> take the risk, if needed. >>>> >>> >>> >>> The checksum's place was selected so that it would be in the >>> same location as UDP's checksum field. How possible it is that >>> SHIM6 will change the checksum location in future drafts, maybe >>> based on the same reason? >>> >> I don't think SHIM6 will bother with that, since the issue is >> there anyway with existing IPv4 UDP only. From my point of view, >> it would be *nice* if we could use existing IPv4 UDP hardware to >> verify the checksum of the HIP header, but the potential ability >> to build hybrid shim6-HIP protocols is much more important. >> Hence, my vote is to give up the checksum compatibility with >> existing IPv4 UDP. >> --Pekka >> _______________________________________________ >> Hipsec mailing list >> Hipsec@lists.ietf.org >> https://www1.ietf.org/mailman/listinfo/hipsec >> > > -- > Gonzalo Camarillo Phone : +358 9 299 33 71 > Oy L M Ericsson Ab Mobile: +358 40 702 35 35 > Telecom R&D Fax : +358 9 299 30 52 > FIN-02420 Jorvas Email : Gonzalo.Camarillo@ericsson.com > Finland http://www.hut.fi/~gonzalo > > _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Wed Oct 19 08:57:02 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESDV8-00053k-E4; Wed, 19 Oct 2005 08:57:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESDV6-00052g-HF for hipsec@megatron.ietf.org; Wed, 19 Oct 2005 08:57:00 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA14444 for ; Wed, 19 Oct 2005 08:56:50 -0400 (EDT) Received: from n2.nomadiclab.com ([193.234.219.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESDgn-0002XD-AU for hipsec@ietf.org; Wed, 19 Oct 2005 09:09:08 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) by n2.nomadiclab.com (Postfix) with ESMTP id 28D82212C3D for ; Wed, 19 Oct 2005 15:56:33 +0300 (EEST) Message-ID: <43564280.5060405@nomadiclab.com> Date: Wed, 19 Oct 2005 15:56:32 +0300 From: Petri Jokela User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: hipsec@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: 7bit Cc: Subject: [Hipsec] HIP base draft - pre 19.10.2005 X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org Hi, I uploaded a new version of the base draft to our server. http://hip4inter.net/drafts.php with txt, html, xml, and diff from the previous pre-version. The date is 191005. The main change was the HIP header modification according to SHIM6 as proposed earlier by Pekka. I didn't give any reason in the text, why there are two fixed bits in the HIP header. Somehow I feel that something should be said. On the other hand it is vague to refer to SHIM6 work if they don't have anything on paper related to this new header structure. Comments? /petri _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Wed Oct 19 09:17:43 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESDp9-0006iR-GW; Wed, 19 Oct 2005 09:17:43 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESDp8-0006hW-P9 for hipsec@megatron.ietf.org; Wed, 19 Oct 2005 09:17:42 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15849 for ; Wed, 19 Oct 2005 09:17:33 -0400 (EDT) Received: from n2.nomadiclab.com ([193.234.219.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESE0s-0003B6-Kl for hipsec@ietf.org; Wed, 19 Oct 2005 09:29:51 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) by n2.nomadiclab.com (Postfix) with ESMTP id BF404212C3D; Wed, 19 Oct 2005 16:17:32 +0300 (EEST) In-Reply-To: <43564280.5060405@nomadiclab.com> References: <43564280.5060405@nomadiclab.com> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <4022AAE5-1B30-4297-AF79-6A85BF4783B0@nomadiclab.com> Content-Transfer-Encoding: 7bit From: Pekka Nikander Subject: Re: [Hipsec] HIP base draft - pre 19.10.2005 Date: Wed, 19 Oct 2005 15:17:30 +0200 To: Petri Jokela X-Mailer: Apple Mail (2.734) X-Spam-Score: 0.0 (/) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 Content-Transfer-Encoding: 7bit Cc: hipsec@ietf.org X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org Thanks, Petri! draft-ietf-ipsec-ikev2-algorithms-00 should be -05 I *think* (please check) that RFC 2541 defines Blowfish CBC; it might be a better reference than [Schneier96]. draft-ietf-hip-arch-01 is now -03 I think some other drafts are also referring to old versions. It would be *very* nice to have the state diagram as a PNG or SVG in the HTML version... Section 4.4.2 would definitely look better if it was recoded as a table, using the new table structure in xml2rfc. For the fixed bits, I think it is sufficient to say "The two fixed bits in the header are reserved for potential SHIM6 compatibility [draft-ietf-shim6-proto-01]. For implementations adhering (only) to this specification, they MUST be set as shown when sending and MUST be ignored when receiving. This is to ensure optimal forward compatibility. Note that implementations that implement other compatible specifications in addition to this specification, the corresponding rules may well be different. For example, in the case that the forthcoming SHIM6 protocol happens to be compatible with this specification, an implementation that implements both this specification and the SHIM6 protocol may need to check these bits in order to determine how to handle the packet." Or something like that. A table summarising the packet types would be nice somewhere in 5.3. It *might* be wise to bump up the codes for packets types beyond R2 to be greater than 16, in order to leave the space between 5 and 15 for SHIM6. Opinions? Note that SHIM6 currently uses I1-R2 in a similar way to HIP, and I don't see any difficulty in sharing them. There are probably other editorial nits, but other than that I think we start to be done. --Pekka _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Thu Oct 20 04:09:52 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESVUm-0007LD-Cz; Thu, 20 Oct 2005 04:09:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESVUk-0007L4-Do for hipsec@megatron.ietf.org; Thu, 20 Oct 2005 04:09:50 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23595 for ; Thu, 20 Oct 2005 04:09:40 -0400 (EDT) Received: from nwkea-mail-2.sun.com ([192.18.42.14]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESVgb-00076V-F3 for hipsec@ietf.org; Thu, 20 Oct 2005 04:22:08 -0400 Received: from jurassic.eng.sun.com ([129.146.68.130]) by nwkea-mail-2.sun.com (8.12.10/8.12.9) with ESMTP id j9K89jh0008139; Thu, 20 Oct 2005 01:09:45 -0700 (PDT) Received: from [129.157.211.182] (dhcp-gnb07-211-182.France.Sun.COM [129.157.211.182]) by jurassic.eng.sun.com (8.13.5+Sun/8.13.5) with ESMTP id j9K89gFI740673 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 20 Oct 2005 01:09:44 -0700 (PDT) Message-ID: <435750C1.3020102@sun.com> Date: Thu, 20 Oct 2005 01:09:37 -0700 From: Erik Nordmark User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050720) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pekka Nikander Subject: Re: [Hipsec] SHIM6 adopting HIP packet format & small change to theformat References: <77F357662F8BFA4CA7074B0410171B6DC9E391@XCH-NW-5V1.nw.nos.boeing.com> <435360DE.1010908@nomadiclab.com> <971F5700-F5FC-4500-AECF-A463DED58E11@nomadiclab.com> In-Reply-To: <971F5700-F5FC-4500-AECF-A463DED58E11@nomadiclab.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Content-Transfer-Encoding: 7bit Cc: hipsec@ietf.org X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org Pekka Nikander wrote: > I don't think SHIM6 will bother with that, since the issue is there > anyway with existing IPv4 UDP only. From my point of view, it would be > *nice* if we could use existing IPv4 UDP hardware to verify the > checksum of the HIP header, but the potential ability to build hybrid > shim6-HIP protocols is much more important. Hence, my vote is to give > up the checksum compatibility with existing IPv4 UDP. FWIW *verifying* TCP/UDP checksums can be done independently of the location of the checksum field. *generation* of the checksums on transmit does require the HW knowing (or being told) where the checksum result should go. But both SHIM6 and HIP are control protocols, thus one wouldn't expect to see a large sustained stream of them. Erik _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Fri Oct 21 09:15:33 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESwk9-0004qP-O3; Fri, 21 Oct 2005 09:15:33 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ESwk7-0004oN-L5 for hipsec@megatron.ietf.org; Fri, 21 Oct 2005 09:15:31 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20778 for ; Fri, 21 Oct 2005 09:15:20 -0400 (EDT) Received: from n2.nomadiclab.com ([193.234.219.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESwwF-0000Qu-GS for hipsec@ietf.org; Fri, 21 Oct 2005 09:28:04 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) by n2.nomadiclab.com (Postfix) with ESMTP id 80EC7212ED5; Fri, 21 Oct 2005 16:14:58 +0300 (EEST) Message-ID: <4358E9D0.1090804@nomadiclab.com> Date: Fri, 21 Oct 2005 16:14:56 +0300 From: Petri Jokela User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pekka Nikander Subject: Re: [Hipsec] HIP base draft - pre 19.10.2005 References: <43564280.5060405@nomadiclab.com> <4022AAE5-1B30-4297-AF79-6A85BF4783B0@nomadiclab.com> In-Reply-To: <4022AAE5-1B30-4297-AF79-6A85BF4783B0@nomadiclab.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca Content-Transfer-Encoding: 7bit Cc: hipsec@ietf.org X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org I uploaded an edited version of the base draft: http://hip4inter.net/drafts.php The current version is dated 211005. See also comments below. > I *think* (please check) that RFC 2541 defines Blowfish CBC; it might > be a better reference than [Schneier96]. I changed the reference to RFC2451. > draft-ietf-hip-arch-01 is now -03 > > I think some other drafts are also referring to old versions. The automatic reference update from resource.org seems not to work properly. They should be up-to-date now. > It would be *very* nice to have the state diagram as a PNG or SVG > in the HTML version... I noticed that the HTML version contains now a _very_optimized_ state diagram ;-) I'll update that next week. > Section 4.4.2 would definitely look better if it was recoded as a > table, using the new table structure in xml2rfc. I hope it is ok now. The xml2rfc table-system is not as flexible as I hoped. Texts and tables are now on "wrong" pages. I'll try to fix that on Monday. If somebody knows either how to put to the left and not centered OR to somehow force to be on the same page as following table, I would appreciate that information. > For the fixed bits, I think it is sufficient to say ... Added text. > A table summarising the packet types would be nice somewhere in 5.3. Added a table. > It *might* be wise to bump up the codes for packets types beyond R2 to > be greater than 16, in order to leave the space between 5 and 15 for > SHIM6. Opinions? Note that SHIM6 currently uses I1-R2 in a similar > way to HIP, and I don't see any difficulty in sharing them. I changed the numbering. Please send comments on that! I can still edit it before IETF submission on Monday. /petri _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Mon Oct 24 08:36:31 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EU1Z1-0003Jq-Le; Mon, 24 Oct 2005 08:36:31 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EU1Yz-0003Jh-RG for hipsec@megatron.ietf.org; Mon, 24 Oct 2005 08:36:30 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06924 for ; Mon, 24 Oct 2005 08:36:15 -0400 (EDT) Received: from n2.nomadiclab.com ([193.234.219.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EU1lj-0001rq-GV for hipsec@ietf.org; Mon, 24 Oct 2005 08:49:40 -0400 Received: from [127.0.0.1] (localhost [127.0.0.1]) by n2.nomadiclab.com (Postfix) with ESMTP id E067E21301B; Mon, 24 Oct 2005 15:36:18 +0300 (EEST) In-Reply-To: <4354DF75.9030306@ericsson.com> References: <4354DF75.9030306@ericsson.com> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <84883481-3AB0-4C61-A1E1-2D4DDDD27284@nomadiclab.com> Content-Transfer-Encoding: 7bit From: Pekka Nikander Subject: Re: [Hipsec] WGLC draft-ietf-hip-dns-03.txt Date: Mon, 24 Oct 2005 14:36:07 +0200 To: HIP X-Mailer: Apple Mail (2.734) X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Content-Transfer-Encoding: 7bit Cc: Julien Laganier X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org While being an author of the draft and therefore considering the draft pretty good, I'd like to get the WG's opinion on a few issues on the draft: 1. Is the introduction too long? Would it be desirable to cut some text from there, and if yes, what? 2. Is the approach right? Might it be better, for example, to define just a single new RR, which would contain the HIT, HI, and RVS domain name? Given the current design, the resolve needs to send DNS queries for A, AAAA, HIPHI and HIPRVS in order to get all data it needs. With the alternative design, it would first ask for HIPHI, and then based on whether there is an RVS name, A and/or AAAA of either the host itself or its RVS server. 3. Are the details fine? 4. Is there something unnecessary (beyond the introduction), something that should be left out? --Pekka _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Thu Oct 27 02:50:51 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EV1b9-0007zH-Mv; Thu, 27 Oct 2005 02:50:51 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EV1aO-0007ke-EK; Thu, 27 Oct 2005 02:50:04 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28132; Thu, 27 Oct 2005 02:49:49 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EV1ng-0003G8-Fn; Thu, 27 Oct 2005 03:03:49 -0400 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1EV1aL-00070z-SJ; Thu, 27 Oct 2005 02:50:01 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Thu, 27 Oct 2005 02:50:01 -0400 X-Spam-Score: 0.4 (/) X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1 Cc: hipsec@ietf.org Subject: [Hipsec] I-D ACTION:draft-ietf-hip-base-04.txt X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Host Identity Protocol Working Group of the IETF. Title : Host Identity Protocol Author(s) : R. Moskowitz, et al. Filename : draft-ietf-hip-base-04.txt Pages : 99 Date : 2005-10-26 This memo specifies the details of the Host Identity Protocol (HIP). HIP allows consenting hosts to securely establish and maintain shared IP-layer state, allowing separation of the identifier and locator roles of IP addresses, thereby enabling continuity of communications across IP address changes. HIP is based on a Sigma-compliant Diffie- Hellman key exchange, using public-key identifiers from a new Host Identity name space for mutual peer authentication. The protocol is designed to be resistant to Denial-of-Service (DoS) and Man-in-the- middle (MitM) attacks, and when used together with another suitable security protocol, such as Encapsulated Security Payload (ESP), it provides integrity protection and optional encryption for upper layer protocols, suchs as TCP and UDP. Discussion related to this document is going on at the IETF HIP Working Group mailing list. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hip-base-04.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-hip-base-04.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-hip-base-04.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-10-26185414.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-hip-base-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-hip-base-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-10-26185414.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec --NextPart-- From hipsec-bounces@lists.ietf.org Thu Oct 27 02:50:52 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EV1bA-0007zj-6y; Thu, 27 Oct 2005 02:50:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EV1aO-0007kG-0h; Thu, 27 Oct 2005 02:50:04 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28127; Thu, 27 Oct 2005 02:49:48 -0400 (EDT) Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EV1ng-0003GB-G6; Thu, 27 Oct 2005 03:03:49 -0400 Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1EV1aL-000714-TK; Thu, 27 Oct 2005 02:50:01 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Thu, 27 Oct 2005 02:50:01 -0400 X-Spam-Score: 0.4 (/) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Cc: hipsec@ietf.org Subject: [Hipsec] I-D ACTION:draft-ietf-hip-esp-01.txt X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Host Identity Protocol Working Group of the IETF. Title : Using ESP transport format with HIP Author(s) : P. Jokela, et al. Filename : draft-ietf-hip-esp-01.txt Pages : 32 Date : 2005-10-26 This memo specifies an Encapsulated Security Payload (ESP) based mechanism for transmission of user data packets, to be used with the Host Identity Protocol (HIP). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hip-esp-01.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-hip-esp-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-hip-esp-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-10-26185743.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-hip-esp-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-hip-esp-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-10-26185743.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec --NextPart-- From hipsec-bounces@lists.ietf.org Fri Oct 28 02:16:31 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVNXT-0004KY-Bf; Fri, 28 Oct 2005 02:16:31 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVNXO-0004E8-JU for hipsec@megatron.ietf.org; Fri, 28 Oct 2005 02:16:29 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24646 for ; Fri, 28 Oct 2005 02:16:09 -0400 (EDT) Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVNkn-0002TH-0N for hipsec@ietf.org; Fri, 28 Oct 2005 02:30:24 -0400 Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 0BAFFC77; Fri, 28 Oct 2005 08:16:09 +0200 (CEST) Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 28 Oct 2005 08:15:20 +0200 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 28 Oct 2005 08:15:20 +0200 Received: from [131.160.36.33] (unknown [131.160.36.33]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 869D9227A; Fri, 28 Oct 2005 09:15:20 +0300 (EEST) Message-ID: <4361C1F8.2070502@ericsson.com> Date: Fri, 28 Oct 2005 09:15:20 +0300 From: Gonzalo Camarillo User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: HIP Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 28 Oct 2005 06:15:20.0708 (UTC) FILETIME=[F972D440:01C5DB86] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Content-Transfer-Encoding: 7bit Cc: David Ward Subject: [Hipsec] Agenda requests for Vancouver X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org Folks, we have already received a few agenda requests. If you would like to request a time slot, send an email to the chairs. Thanks, Gonzalo HIP co-chair _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Fri Oct 28 05:45:51 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVQo3-0003Cp-B5; Fri, 28 Oct 2005 05:45:51 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVQo1-0003Cg-Dg for hipsec@megatron.ietf.org; Fri, 28 Oct 2005 05:45:49 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04341 for ; Fri, 28 Oct 2005 05:45:32 -0400 (EDT) Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVR1T-00089x-TV for hipsec@ietf.org; Fri, 28 Oct 2005 05:59:49 -0400 Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id DCF324F0025; Fri, 28 Oct 2005 11:45:25 +0200 (CEST) Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 28 Oct 2005 11:45:02 +0200 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 28 Oct 2005 11:45:01 +0200 Received: from [131.160.36.33] (unknown [131.160.36.33]) by mail.lmf.ericsson.se (Postfix) with ESMTP id CE523227A; Fri, 28 Oct 2005 12:45:01 +0300 (EEST) Message-ID: <4361F31D.5090700@ericsson.com> Date: Fri, 28 Oct 2005 12:45:01 +0300 From: Gonzalo Camarillo User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pekka Nikander References: <02215F9C-9164-4632-9C88-85F607A2A0EA@nomadiclab.com> In-Reply-To: <02215F9C-9164-4632-9C88-85F607A2A0EA@nomadiclab.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 28 Oct 2005 09:45:01.0896 (UTC) FILETIME=[446BC480:01C5DBA4] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab Content-Transfer-Encoding: 7bit Cc: hipsec@ietf.org Subject: [Hipsec] Re: Start re-chartering discussion in Vancouver? X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org Hi Pekka, yes, our charter says that as soon as we finalize our chartered items (which happen fairly soon), we need to conclude or recharter. In order to recharter the WG, we need to have new topics and people comitted to work on them. We welcome discussions and comments on this issue. Thanks, Gonzalo Pekka Nikander wrote: > Dear HIP WG chairs, > > Should we start HIP WG re-chartering discussion in Vancouver, with the > intention of having a new charter proposal available before the Dallas > meeting? > > --Pekka > _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Fri Oct 28 10:03:33 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVUpR-0003Mi-Ir; Fri, 28 Oct 2005 10:03:33 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVUpQ-0003LB-AB for hipsec@megatron.ietf.org; Fri, 28 Oct 2005 10:03:32 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19239 for ; Fri, 28 Oct 2005 10:03:14 -0400 (EDT) Received: from smtp0.netlab.nec.de ([195.37.70.40]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVV2z-0006rE-6Z for hipsec@ietf.org; Fri, 28 Oct 2005 10:17:34 -0400 Received: by smtp0.netlab.nec.de (Postfix, from userid 502) id 4B6C41C934; Fri, 28 Oct 2005 16:03:21 +0200 (CEST) Received: from ganymede.students (ganymede.students [10.1.2.1]) by smtp0.netlab.nec.de (Postfix) with ESMTP id 9546BDC57; Fri, 28 Oct 2005 16:03:18 +0200 (CEST) Received: from miriam ([10.1.2.130]) by ganymede.students with Microsoft SMTPSVC(6.0.3790.1830); Fri, 28 Oct 2005 11:30:20 +0200 From: Miriam Esteban To: hipsec@ietf.org, Lars Eggert , Julien Laganier Date: Fri, 28 Oct 2005 11:30:13 +0200 User-Agent: KMail/1.8 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510281130.14106.miriam.esteban@netlab.nec.de> X-OriginalArrivalTime: 28 Oct 2005 09:30:20.0051 (UTC) FILETIME=[36CCE630:01C5DBA2] X-Spam-Status: No, score=-5.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on atlas.office X-Sanitizer: This message has been sanitized! X-Spam-Score: 0.0 (/) X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a Content-Transfer-Encoding: 7bit Cc: Subject: [Hipsec] How to maintain a registered service? X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org Dear all, While rereading the drafts about rvs and registration I have seen that there is nothing defined yet about how to maintain this registration alive. I have one proposal for this. This consists of the REQUESTER sending one UPDATE packet with a REG_REQUEST parameter to the REGISTRAR. This packet should be send before the lifetime of the registered service is finished. If not, the REGISTRAR should remove the services registered by the REQUESTER. +-----+ +-----+-----+ | | | | | | | UPDATE(REG_REQ:S) | | | |RQ | ----------------------------> | R | S | | | | | | | | UPDATE(REG_RESP:S)| | | | | <-------------------------- | | | +-----+ +-----+-----+ This proposal conflicts with what it is said in draft-ietf-hip-registration-00. "Moreover, the requester MUST NOT include the parameter unless the registrar's R1 packet or latest received UPDATE packet has contained a REG_INFO parameter with the requested registration types." --- Talking about REG_REQUEST parameter---- Then, this maintaining process as it's explained here should be like it's reported in the draft: +-----+ +-----+-----+ | | UPDATE(REG_INFO:S) | | | | | <-------------------------- | | | | | | | | | | UPDATE(REG_REQ:S) | | | |RQ | ----------------------------> | R | S | | | | | | | | UPDATE(REG_RESP:S) | | | | | <-------------------------- | | | +-----+ +-----+-----+ I don't see why it's necessary that the REGISTRAR is the one to trigger this process in the service maintainance. Maybe because the lifetimes are supposed quite big and the information about the services might have changed? What happens if the REQUESTER changes its IP address at the same moment before receiving the REG_INFO? Does the REGISTRAR have to start retransmitting the UPDATE with the REG_INFO parameter? I don't really see why it should be like this. Could you please help me with that? I do really think this is an issue one of these documents should include. For instance, it would be a part to add (as I see it) as point 3.4 in draf-ietf-hip-rvs-04. Also in point 5 in draft-ietf-hip-registration-00. Or maybe it's not there because it's considered an implementation issue? Thanks! Miriam _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Fri Oct 28 11:16:35 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVVy7-00010O-4l; Fri, 28 Oct 2005 11:16:35 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVVy5-00010D-Uk for hipsec@megatron.ietf.org; Fri, 28 Oct 2005 11:16:34 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23928 for ; Fri, 28 Oct 2005 11:16:17 -0400 (EDT) Received: from mx.laposte.net ([81.255.54.11]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVWBc-0000c7-6b for hipsec@ietf.org; Fri, 28 Oct 2005 11:30:36 -0400 Received: from [192.168.1.105] (212.119.9.178) by mx.laposte.net (7.2.060.1) (authenticated as julien.laganier) id 4329511C01E24041; Fri, 28 Oct 2005 17:16:12 +0200 From: Julien Laganier To: Miriam Esteban Subject: Re: [Hipsec] How to maintain a registered service? Date: Fri, 28 Oct 2005 17:18:02 +0200 User-Agent: KMail/1.8 References: <200510281130.14106.miriam.esteban@netlab.nec.de> In-Reply-To: <200510281130.14106.miriam.esteban@netlab.nec.de> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200510281718.02666.julien.IETF@laposte.net> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Spam-Score: 0.1 (/) X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2 Content-Transfer-Encoding: 7bit Cc: Lars Eggert , hipsec@ietf.org X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org Hi Miriam, Thanks for bringing this issue to our attention. More thoughts are inlined below: On Friday 28 October 2005 11:30, Miriam Esteban wrote: > Dear all, > > While rereading the drafts about rvs and registration I have > seen that there is nothing defined yet about how to maintain this > registration alive. I don't think that the specification does not allow a requester to prolong a registration. > I have one proposal for this. > This consists of the REQUESTER sending one UPDATE packet with a > REG_REQUEST parameter to the REGISTRAR. This packet should be send > before the lifetime of the registered service is finished. If not, > the REGISTRAR should remove the services registered by the > REQUESTER. +-----+ +-----+-----+ | | UPDATE(REG_REQ:S) | | | | RQ |---------------------------->| R | S | | | UPDATE(REG_RESP:S) | | | | |<----------------------------| | | +-----+ +-----+-----+ > > This proposal conflicts with what it is said in > draft-ietf-hip-registration-00. > > "Moreover, the requester MUST NOT include the > parameter unless the registrar's R1 packet or latest received > UPDATE packet has contained a REG_INFO parameter with the requested > registration types." > --- Talking about REG_REQUEST parameter---- > > Then, this maintaining process as it's explained here should be > like it's reported in the draft: > +-----+ +-----+-----+ | | UPDATE(REG_INFO:S) | | | | |<----------------------------| | | | | UPDATE(REG_REQ:S) | | | | RQ |---------------------------->| R | S | | | UPDATE(REG_RESP:S) | | | | |<----------------------------| | | +-----+ +-----+-----+ > I don't see why it's necessary that the REGISTRAR is the one to > trigger this process in the service maintainance. Maybe because the > lifetimes are supposed quite big and the information about the > services might have changed? It does not conflict. If a registration types is available (i.e. announced in R1 or UPDATE) the requester to re-register before the registration expire (i.e. prolong it). What is forbidden is to register with a service currently unavailable (i.e. not announced in R1 or in the last UPDATE.) In other words, a prolongation via another REG_REQ, REG_REP exchange does not require that an UPDATE is sent by the registrar before hand. If people think that is unclear maybe we need to clarify this point. > What happens if the REQUESTER changes > its IP address at the same moment before receiving the REG_INFO? > Does the REGISTRAR have to start retransmitting the UPDATE with the > REG_INFO parameter? The requester changing its IP address is IMO orthogonal to the registration maintenance. The requester would notify the registrar by sending an UPDATE containing a LOCATOR with its new IP address. Then the registrar would update its location table. > I don't really see why it should be like this. > Could you please help me with that? I hope the above clarify things... > Or maybe it's not there because it's considered an implementation > issue? I think it the current specification forbids neither to prolong a registration, nor to update the requester IP address (FWIW even the registrar can update its IP address.) So IMHO it is implicit that a registration can be prolonged, but as I said before, if people think that a clarification is necessary then we could do that. Thanks again. --julien _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Sat Oct 29 07:10:41 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVobh-0006zr-Qx; Sat, 29 Oct 2005 07:10:41 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVobg-0006zm-NH for hipsec@megatron.ietf.org; Sat, 29 Oct 2005 07:10:40 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24895 for ; Sat, 29 Oct 2005 07:10:23 -0400 (EDT) Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVopM-0008FY-SA for hipsec@ietf.org; Sat, 29 Oct 2005 07:24:54 -0400 Received: from esealmw126.eemea.ericsson.se (unknown [153.88.254.123]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id F1654528; Sat, 29 Oct 2005 13:10:23 +0200 (CEST) Received: from esealmw128.eemea.ericsson.se ([153.88.254.172]) by esealmw126.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Sat, 29 Oct 2005 13:04:52 +0200 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Sat, 29 Oct 2005 13:04:52 +0200 Received: from [131.160.126.79] (rvi2-126-79.lmf.ericsson.se [131.160.126.79]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 225DE2358; Sat, 29 Oct 2005 14:04:52 +0300 (EEST) Message-ID: <43635752.8090204@ericsson.com> Date: Sat, 29 Oct 2005 14:04:50 +0300 From: Gonzalo Camarillo User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: HIP Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 29 Oct 2005 11:04:52.0488 (UTC) FILETIME=[963FD880:01C5DC78] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: 08e48e05374109708c00c6208b534009 Content-Transfer-Encoding: 7bit Cc: David Ward Subject: [Hipsec] Draft agenda IETF 64 X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org Folks, here you have our draft agenda for Vancouver: http://hip.piuha.net/meetings/ietf64/agenda-hip.html Cheers, Gonzalo _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Sun Oct 30 03:38:26 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EW8hu-0003Ym-M7; Sun, 30 Oct 2005 03:38:26 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EW8hs-0003Yb-VJ for hipsec@megatron.ietf.org; Sun, 30 Oct 2005 03:38:25 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22453 for ; Sun, 30 Oct 2005 03:38:05 -0500 (EST) Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EW8vk-0007Lh-9P for hipsec@ietf.org; Sun, 30 Oct 2005 03:52:49 -0500 Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 8065F6DE; Sun, 30 Oct 2005 09:38:06 +0100 (CET) Received: from esealmw127.eemea.ericsson.se ([153.88.254.175]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Sun, 30 Oct 2005 09:38:03 +0100 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Sun, 30 Oct 2005 09:38:03 +0100 Received: from [131.160.126.30] (rvi2-126-30.lmf.ericsson.se [131.160.126.30]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 02174235F; Sun, 30 Oct 2005 10:38:03 +0200 (EET) Message-ID: <4364866B.9090105@ericsson.com> Date: Sun, 30 Oct 2005 10:38:03 +0200 From: Gonzalo Camarillo User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: HIP Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 30 Oct 2005 08:38:03.0893 (UTC) FILETIME=[3E54AA50:01C5DD2D] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 Content-Transfer-Encoding: 7bit Cc: David Ward Subject: [Hipsec] Official meeting material site X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org Folks, FYI: the IETF has set up a site that will contain the meeting material for the IETF 64, including WG agendas, presentations, notes, and minutes. In short, the information we usually store in the meeting area of our supplemental web page. https://datatracker.ietf.org/public/meeting_materials.cgi?meeting_num=64 Note that we will still be using our supplemental web page as well. We will try and keep both pages synchronized. When we get more operational experience with the new page, we will see if it makes sense to store some of the material only on the official page. Cheers, Gonzalo HIP co-chair _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Sun Oct 30 14:19:06 2005 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EWIht-0004BS-SY; Sun, 30 Oct 2005 14:19:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EWIhr-0004Au-MS for hipsec@megatron.ietf.org; Sun, 30 Oct 2005 14:19:04 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04761 for ; Sun, 30 Oct 2005 14:18:41 -0500 (EST) Received: from rat01037.dc-ratingen.de ([195.233.129.142]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EWHrH-00051I-Pc for hipsec@ietf.org; Sun, 30 Oct 2005 13:24:49 -0500 Received: from heinz.vodafone-is.de (heinz_e0 [195.233.128.26]) by rat01037.dc-ratingen.de (Switch-3.1.4/Switch-3.1.0) with ESMTP id j9UI9f9L006551 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 30 Oct 2005 19:09:41 +0100 (MET) Received: from gpsmxr04.gps.internal.vodafone.com ([195.232.231.115]) by heinz.vodafone-is.de (Switch-3.1.4/Switch-3.1.0) with ESMTP id j9UI9fPF011340; Sun, 30 Oct 2005 19:09:41 +0100 (MET) Received: from gpsmx10.gps.internal.vodafone.com ([145.230.1.20]) by gpsmxr04.gps.internal.vodafone.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 30 Oct 2005 19:09:41 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5.7232.53 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C5DD7D.181DB72A" Date: Sun, 30 Oct 2005 18:09:28 -0000 Message-ID: X-MS-Has-Attach: yes Thread-Topic: I-D ACTION:draft-papadoglou-hiprg-hit-presence-00.txt Thread-Index: AcXUJmH0bZhtWG/LSHWUxOZenn8dkgAy4N0gAiKtZlA= From: "Papadoglou, Nick, VF-Group" To: X-OriginalArrivalTime: 30 Oct 2005 18:09:41.0527 (UTC) FILETIME=[19504A70:01C5DD7D] X-Spam-Score: 0.0 (/) X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b Cc: hipsec@ietf.org Subject: [Hipsec] I-D ACTION:draft-papadoglou-hiprg-hit-presence-00.txt X-BeenThere: hipsec@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "This is the official IETF Mailing List for the HIP Working Group." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: hipsec-bounces@lists.ietf.org Errors-To: hipsec-bounces@lists.ietf.org This is a multi-part message in MIME format. ------_=_NextPart_001_01C5DD7D.181DB72A Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Dear all, Please find below a new ID that we submitted and we intent to present/discuss in the Vancouver meeting. Your comments/suggestions and constructive comments are more than welcome.=20 Best regards, Nick -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] Sent: Tuesday, October 18, 2005 12:50 PM To: i-d-announce@ietf.org Subject: I-D ACTION:draft-papadoglou-hiprg-hit-presence-00.txt=20 A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Host Identity Tags (HIT) in Presence Information Data Format (PIDF)=20 Author(s) : N. Papadoglou, H. Zisimopoulos Filename : draft-papadoglou-hiprg-hit-presence-00.txt Pages : 11 Date : 2005-10-18 =09 This document describes a new way of exchanging Host Identities (or=20 Host Identity Tags) by means of the Presence Information Data Format=20 [6] using the Host Identity Protocol (HIP). A new presence=20 information element is proposed as an extension to the Presence=20 Information Data Format (PIDF), to include and convey the Host=20 Identity that corresponds to the different SIP URI's the node may=20 have registered. This automatically creates a list of associations=20 between the SIP URI and the Host identity for the different UA=20 instances on the same or different node.=20 =20 A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-papadoglou-hiprg-hit-presence- 00.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. =20 You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-papadoglou-hiprg-hit-presence-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-papadoglou-hiprg-hit-presence-00.txt". =09 NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. =09 =09 Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. ------_=_NextPart_001_01C5DD7D.181DB72A Content-Type: application/octet-stream; name="draft-papadoglou-hiprg-hit-presence-00.URL" Content-Description: draft-papadoglou-hiprg-hit-presence-00.URL Content-Disposition: attachment; filename="draft-papadoglou-hiprg-hit-presence-00.URL" Content-Transfer-Encoding: base64 W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0 cy9kcmFmdC1wYXBhZG9nbG91LWhpcHJnLWhpdC1wcmVzZW5jZS0wMC50eHQNCg== ------_=_NextPart_001_01C5DD7D.181DB72A Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec ------_=_NextPart_001_01C5DD7D.181DB72A--