From hipsec-bounces@lists.ietf.org Fri Jun 02 08:28:19 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fm8lF-0005ns-OA; Fri, 02 Jun 2006 08:28:17 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fm8lF-0005nn-3F for hipsec@ietf.org; Fri, 02 Jun 2006 08:28:17 -0400 Received: from mh1.eu.ntt.net ([212.119.0.10]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1Fm8lD-0006Nr-6g for hipsec@ietf.org; Fri, 02 Jun 2006 08:28:16 -0400 Received: (qmail 32424 invoked by uid 2101); 2 Jun 2006 13:28:13 +0100 Received: from julien.IETF@laposte.net by mh1 by uid 0 with qmail-scanner-1.22st (clamdscan: 0.85.1. spamassassin: 3.0.4. perlscan: 1.22st. Clear:RC:1(212.119.9.178):. Processed in 0.080565 secs); 02 Jun 2006 12:28:13 -0000 Received: from unknown (HELO ?192.168.1.105?) (212.119.9.178) by mx1.eu.ntt.net with SMTP; 2 Jun 2006 13:28:13 +0100 From: Julien Laganier To: HIP Date: Fri, 2 Jun 2006 14:28:17 +0200 User-Agent: KMail/1.8.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200606021428.18306.julien.IETF@laposte.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Cc: Pekka Nikander Subject: [Hipsec] Storing ORCHIDs/HITs under a /28 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: , Errors-To: hipsec-bounces@lists.ietf.org Folks, The proposed ORCHID prefix length of 8-bits has been discussed on both HIPsec and int-area ML. Some persons have objected that allocation because they believe an 8-bits prefix is too short by some. We had an offline discussion in the hope to find a solution acceptable for both parties, and we eventually agreed that allocation of a /28 is the way to move forward. Therefore, I'd like to confirm with the HIP WG that storing ORCHIDs (hence HITs) under a /28 prefix is acceptable. The implication is that the public key hash would be truncated to 100-bits. If you agree or disagree with that proposal, please say so ASAP (say before next Friday, the 9th) so we can move forward and resubmit the ORCHID draft before the cut-off. Thanks, --julien _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Fri Jun 02 09:16:26 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fm9Vm-0003Ru-Ru; Fri, 02 Jun 2006 09:16:22 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fm9Vl-0003LW-Eg for hipsec@ietf.org; Fri, 02 Jun 2006 09:16:21 -0400 Received: from dsl092-066-146.bos1.dsl.speakeasy.net ([66.92.66.146] helo=alva.home) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fm9Vk-0004nu-6b for hipsec@ietf.org; Fri, 02 Jun 2006 09:16:21 -0400 Received: from shep (helo=alva.home) by alva.home with local-esmtp (Exim 3.36 #1 (Debian)) id 1Fm9VX-0004Kn-00; Fri, 02 Jun 2006 09:16:07 -0400 From: Tim Shepard To: Julien Laganier Subject: Re: [Hipsec] Storing ORCHIDs/HITs under a /28 In-reply-to: Your message of Fri, 02 Jun 2006 14:28:17 +0200. <200606021428.18306.julien.IETF@laposte.net> Date: Fri, 02 Jun 2006 09:16:07 -0400 Message-Id: X-Spam-Score: 0.1 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Cc: HIP , Pekka Nikander 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: , Errors-To: hipsec-bounces@lists.ietf.org > Therefore, I'd like to confirm with the HIP WG that storing ORCHIDs > (hence HITs) under a /28 prefix is acceptable. The implication is > that the public key hash would be truncated to 100-bits. ("storing" seems like a poor choice for a verb here.) I find the /28 prefix to be inexplicably long. I can understand that someone might object to a prefix length of /8, but how that objection continued until 20 more bits had been added to the prefix, well, I really wonder. Please explain. (How many random 100-bit strings have to be generated before the probability of a duplication has crossed over the one-in-a-million threshold? I'll try to estimate this sometime this weekend.) -Tim Shepard shep@alum.mit.edu _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Fri Jun 02 10:05:28 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FmAHG-00073O-Np; Fri, 02 Jun 2006 10:05:26 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FmAHF-00070T-9z for hipsec@lists.ietf.org; Fri, 02 Jun 2006 10:05:25 -0400 Received: from mh1.eu.ntt.net ([212.119.0.10]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FmAHC-0001HW-Fi for hipsec@lists.ietf.org; Fri, 02 Jun 2006 10:05:25 -0400 Received: (qmail 9321 invoked by uid 2101); 2 Jun 2006 15:05:21 +0100 Received: from julien.IETF@laposte.net by mh1 by uid 0 with qmail-scanner-1.22st (clamdscan: 0.85.1. spamassassin: 3.0.4. perlscan: 1.22st. Clear:RC:1(212.119.9.178):. Processed in 0.107228 secs); 02 Jun 2006 14:05:21 -0000 Received: from unknown (HELO ?192.168.1.105?) (212.119.9.178) by mx1.eu.ntt.net with SMTP; 2 Jun 2006 15:05:21 +0100 From: Julien Laganier To: hipsec@lists.ietf.org Subject: Re: [Hipsec] Storing ORCHIDs/HITs under a /28 Date: Fri, 2 Jun 2006 16:05:25 +0200 User-Agent: KMail/1.8.2 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200606021605.26291.julien.IETF@laposte.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca Cc: HIP , Pekka Nikander 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: , Errors-To: hipsec-bounces@lists.ietf.org On Friday 02 June 2006 15:16, Tim Shepard wrote: > > Therefore, I'd like to confirm with the HIP WG that storing > > ORCHIDs (hence HITs) under a /28 prefix is acceptable. The > > implication is that the public key hash would be truncated to > > 100-bits. > > ("storing" seems like a poor choice for a verb here.) Ok, feel free to enlighten us if you have a better term. I am too busy to do trichotetratomy right now :-> > I find the /28 prefix to be inexplicably long. > > I can understand that someone might object to a prefix length of > /8, but how that objection continued until 20 more bits had been > added to the prefix, well, I really wonder. > > Please explain. We'd like this allocation to be made as an IETF experimental allocation performed by the IANA. IANA has a /23 allocated for that purpose, so our prefix has to be strictly longer than 23, or more (We cannot reasonably ask for say half of the available space.) Given that, 28 seemed sensible. > (How many random 100-bit strings have to be generated before the > probability of a duplication has crossed over the one-in-a-million > threshold? I'll try to estimate this sometime this weekend.) Remember that this is an experimental prefix allocation. If the experiment is successfull we might be able to request for a larger allocation later on. Regarding the collision risk, it looks like the birthday paradox. Wikipedia gives this formula (I didn't spent time to verify the maths): n(p) ~ sqr(2 x N x ln( 1 / (1 - p) ) ) Where: - N is the number of different birthdays (2^100 in our case) - p is a fixed probability (1/1000000 in our case) - p(n) is the probability that a duplicate occurs amongst a population of size n which has uniformly distributed birthdays. - n(p) the smallest n for which the probability p(n) is greater than the given p Result is that n(1/1000000) = 1590 billions. Seems okay to me for a time limited experiment. --julien _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Fri Jun 02 10:05:28 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FmAHG-00073J-IT; Fri, 02 Jun 2006 10:05:26 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FmAHF-00070R-9Q for hipsec@ietf.org; Fri, 02 Jun 2006 10:05:25 -0400 Received: from mh1.eu.ntt.net ([212.119.0.10]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FmAHC-0001HV-Dz for hipsec@ietf.org; Fri, 02 Jun 2006 10:05:25 -0400 Received: (qmail 9308 invoked by uid 2101); 2 Jun 2006 15:05:21 +0100 Received: from julien.IETF@laposte.net by mh1 by uid 0 with qmail-scanner-1.22st (clamdscan: 0.85.1. spamassassin: 3.0.4. perlscan: 1.22st. Clear:RC:1(212.119.9.178):. Processed in 0.056557 secs); 02 Jun 2006 14:05:21 -0000 Received: from unknown (HELO ?192.168.1.105?) (212.119.9.178) by mx1.eu.ntt.net with SMTP; 2 Jun 2006 15:05:21 +0100 From: Julien Laganier To: hipsec@lists.ietf.org Subject: Re: [Hipsec] Storing ORCHIDs/HITs under a /28 Date: Fri, 2 Jun 2006 16:05:25 +0200 User-Agent: KMail/1.8.2 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200606021605.26291.julien.IETF@laposte.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca Cc: HIP , Pekka Nikander 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: , Errors-To: hipsec-bounces@lists.ietf.org On Friday 02 June 2006 15:16, Tim Shepard wrote: > > Therefore, I'd like to confirm with the HIP WG that storing > > ORCHIDs (hence HITs) under a /28 prefix is acceptable. The > > implication is that the public key hash would be truncated to > > 100-bits. > > ("storing" seems like a poor choice for a verb here.) Ok, feel free to enlighten us if you have a better term. I am too busy to do trichotetratomy right now :-> > I find the /28 prefix to be inexplicably long. > > I can understand that someone might object to a prefix length of > /8, but how that objection continued until 20 more bits had been > added to the prefix, well, I really wonder. > > Please explain. We'd like this allocation to be made as an IETF experimental allocation performed by the IANA. IANA has a /23 allocated for that purpose, so our prefix has to be strictly longer than 23, or more (We cannot reasonably ask for say half of the available space.) Given that, 28 seemed sensible. > (How many random 100-bit strings have to be generated before the > probability of a duplication has crossed over the one-in-a-million > threshold? I'll try to estimate this sometime this weekend.) Remember that this is an experimental prefix allocation. If the experiment is successfull we might be able to request for a larger allocation later on. Regarding the collision risk, it looks like the birthday paradox. Wikipedia gives this formula (I didn't spent time to verify the maths): n(p) ~ sqr(2 x N x ln( 1 / (1 - p) ) ) Where: - N is the number of different birthdays (2^100 in our case) - p is a fixed probability (1/1000000 in our case) - p(n) is the probability that a duplicate occurs amongst a population of size n which has uniformly distributed birthdays. - n(p) the smallest n for which the probability p(n) is greater than the given p Result is that n(1/1000000) = 1590 billions. Seems okay to me for a time limited experiment. --julien _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Fri Jun 02 10:05:28 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FmAHG-00073O-Np; Fri, 02 Jun 2006 10:05:26 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FmAHF-00070T-9z for hipsec@lists.ietf.org; Fri, 02 Jun 2006 10:05:25 -0400 Received: from mh1.eu.ntt.net ([212.119.0.10]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FmAHC-0001HW-Fi for hipsec@lists.ietf.org; Fri, 02 Jun 2006 10:05:25 -0400 Received: (qmail 9321 invoked by uid 2101); 2 Jun 2006 15:05:21 +0100 Received: from julien.IETF@laposte.net by mh1 by uid 0 with qmail-scanner-1.22st (clamdscan: 0.85.1. spamassassin: 3.0.4. perlscan: 1.22st. Clear:RC:1(212.119.9.178):. Processed in 0.107228 secs); 02 Jun 2006 14:05:21 -0000 Received: from unknown (HELO ?192.168.1.105?) (212.119.9.178) by mx1.eu.ntt.net with SMTP; 2 Jun 2006 15:05:21 +0100 From: Julien Laganier To: hipsec@lists.ietf.org Subject: Re: [Hipsec] Storing ORCHIDs/HITs under a /28 Date: Fri, 2 Jun 2006 16:05:25 +0200 User-Agent: KMail/1.8.2 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200606021605.26291.julien.IETF@laposte.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca Cc: HIP , Pekka Nikander 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: , Errors-To: hipsec-bounces@lists.ietf.org On Friday 02 June 2006 15:16, Tim Shepard wrote: > > Therefore, I'd like to confirm with the HIP WG that storing > > ORCHIDs (hence HITs) under a /28 prefix is acceptable. The > > implication is that the public key hash would be truncated to > > 100-bits. > > ("storing" seems like a poor choice for a verb here.) Ok, feel free to enlighten us if you have a better term. I am too busy to do trichotetratomy right now :-> > I find the /28 prefix to be inexplicably long. > > I can understand that someone might object to a prefix length of > /8, but how that objection continued until 20 more bits had been > added to the prefix, well, I really wonder. > > Please explain. We'd like this allocation to be made as an IETF experimental allocation performed by the IANA. IANA has a /23 allocated for that purpose, so our prefix has to be strictly longer than 23, or more (We cannot reasonably ask for say half of the available space.) Given that, 28 seemed sensible. > (How many random 100-bit strings have to be generated before the > probability of a duplication has crossed over the one-in-a-million > threshold? I'll try to estimate this sometime this weekend.) Remember that this is an experimental prefix allocation. If the experiment is successfull we might be able to request for a larger allocation later on. Regarding the collision risk, it looks like the birthday paradox. Wikipedia gives this formula (I didn't spent time to verify the maths): n(p) ~ sqr(2 x N x ln( 1 / (1 - p) ) ) Where: - N is the number of different birthdays (2^100 in our case) - p is a fixed probability (1/1000000 in our case) - p(n) is the probability that a duplicate occurs amongst a population of size n which has uniformly distributed birthdays. - n(p) the smallest n for which the probability p(n) is greater than the given p Result is that n(1/1000000) = 1590 billions. Seems okay to me for a time limited experiment. --julien _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Fri Jun 02 10:05:28 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FmAHG-00073J-IT; Fri, 02 Jun 2006 10:05:26 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FmAHF-00070R-9Q for hipsec@ietf.org; Fri, 02 Jun 2006 10:05:25 -0400 Received: from mh1.eu.ntt.net ([212.119.0.10]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FmAHC-0001HV-Dz for hipsec@ietf.org; Fri, 02 Jun 2006 10:05:25 -0400 Received: (qmail 9308 invoked by uid 2101); 2 Jun 2006 15:05:21 +0100 Received: from julien.IETF@laposte.net by mh1 by uid 0 with qmail-scanner-1.22st (clamdscan: 0.85.1. spamassassin: 3.0.4. perlscan: 1.22st. Clear:RC:1(212.119.9.178):. Processed in 0.056557 secs); 02 Jun 2006 14:05:21 -0000 Received: from unknown (HELO ?192.168.1.105?) (212.119.9.178) by mx1.eu.ntt.net with SMTP; 2 Jun 2006 15:05:21 +0100 From: Julien Laganier To: hipsec@lists.ietf.org Subject: Re: [Hipsec] Storing ORCHIDs/HITs under a /28 Date: Fri, 2 Jun 2006 16:05:25 +0200 User-Agent: KMail/1.8.2 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200606021605.26291.julien.IETF@laposte.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca Cc: HIP , Pekka Nikander 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: , Errors-To: hipsec-bounces@lists.ietf.org On Friday 02 June 2006 15:16, Tim Shepard wrote: > > Therefore, I'd like to confirm with the HIP WG that storing > > ORCHIDs (hence HITs) under a /28 prefix is acceptable. The > > implication is that the public key hash would be truncated to > > 100-bits. > > ("storing" seems like a poor choice for a verb here.) Ok, feel free to enlighten us if you have a better term. I am too busy to do trichotetratomy right now :-> > I find the /28 prefix to be inexplicably long. > > I can understand that someone might object to a prefix length of > /8, but how that objection continued until 20 more bits had been > added to the prefix, well, I really wonder. > > Please explain. We'd like this allocation to be made as an IETF experimental allocation performed by the IANA. IANA has a /23 allocated for that purpose, so our prefix has to be strictly longer than 23, or more (We cannot reasonably ask for say half of the available space.) Given that, 28 seemed sensible. > (How many random 100-bit strings have to be generated before the > probability of a duplication has crossed over the one-in-a-million > threshold? I'll try to estimate this sometime this weekend.) Remember that this is an experimental prefix allocation. If the experiment is successfull we might be able to request for a larger allocation later on. Regarding the collision risk, it looks like the birthday paradox. Wikipedia gives this formula (I didn't spent time to verify the maths): n(p) ~ sqr(2 x N x ln( 1 / (1 - p) ) ) Where: - N is the number of different birthdays (2^100 in our case) - p is a fixed probability (1/1000000 in our case) - p(n) is the probability that a duplicate occurs amongst a population of size n which has uniformly distributed birthdays. - n(p) the smallest n for which the probability p(n) is greater than the given p Result is that n(1/1000000) = 1590 billions. Seems okay to me for a time limited experiment. --julien _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Fri Jun 02 10:11:32 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FmAN8-0001Tu-S7; Fri, 02 Jun 2006 10:11:30 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FmAN8-0001Tm-3I; Fri, 02 Jun 2006 10:11:30 -0400 Received: from dsl092-066-146.bos1.dsl.speakeasy.net ([66.92.66.146] helo=alva.home) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FmAN6-0001k8-RS; Fri, 02 Jun 2006 10:11:30 -0400 Received: from shep (helo=alva.home) by alva.home with local-esmtp (Exim 3.36 #1 (Debian)) id 1FmAN3-0004OP-00; Fri, 02 Jun 2006 10:11:25 -0400 From: Tim Shepard To: Julien Laganier Subject: Re: [Hipsec] Storing ORCHIDs/HITs under a /28 In-reply-to: Your message of Fri, 02 Jun 2006 16:05:25 +0200. <200606021605.26291.julien.IETF@laposte.net> Date: Fri, 02 Jun 2006 10:11:25 -0400 Message-Id: X-Spam-Score: 0.1 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Cc: HIP , hipsec@lists.ietf.org, Pekka Nikander 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: , Errors-To: hipsec-bounces@lists.ietf.org > We'd like this allocation to be made as an IETF experimental > allocation performed by the IANA. IANA has a /23 allocated for that > purpose, so our prefix has to be strictly longer than 23, or more (We > cannot reasonably ask for say half of the available space.) > > Given that, 28 seemed sensible. > > Remember that this is an experimental prefix allocation. If the > experiment is successfull we might be able to request for a larger > allocation later on. This explanation helps much. Thanks. Sometimes experiments escape the laboratory and get popular faster than the experimental version can be replaced with a version designed to scale for the real world (e.g. IPv4). -Tim Shepard shep@alum.mit.edu _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Fri Jun 02 10:11:32 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FmAN9-0001Tz-0R; Fri, 02 Jun 2006 10:11:31 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FmAN8-0001Tm-3I; Fri, 02 Jun 2006 10:11:30 -0400 Received: from dsl092-066-146.bos1.dsl.speakeasy.net ([66.92.66.146] helo=alva.home) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FmAN6-0001k8-RS; Fri, 02 Jun 2006 10:11:30 -0400 Received: from shep (helo=alva.home) by alva.home with local-esmtp (Exim 3.36 #1 (Debian)) id 1FmAN3-0004OP-00; Fri, 02 Jun 2006 10:11:25 -0400 From: Tim Shepard To: Julien Laganier Subject: Re: [Hipsec] Storing ORCHIDs/HITs under a /28 In-reply-to: Your message of Fri, 02 Jun 2006 16:05:25 +0200. <200606021605.26291.julien.IETF@laposte.net> Date: Fri, 02 Jun 2006 10:11:25 -0400 Message-Id: X-Spam-Score: 0.1 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Cc: HIP , hipsec@lists.ietf.org, Pekka Nikander 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: , Errors-To: hipsec-bounces@lists.ietf.org > We'd like this allocation to be made as an IETF experimental > allocation performed by the IANA. IANA has a /23 allocated for that > purpose, so our prefix has to be strictly longer than 23, or more (We > cannot reasonably ask for say half of the available space.) > > Given that, 28 seemed sensible. > > Remember that this is an experimental prefix allocation. If the > experiment is successfull we might be able to request for a larger > allocation later on. This explanation helps much. Thanks. Sometimes experiments escape the laboratory and get popular faster than the experimental version can be replaced with a version designed to scale for the real world (e.g. IPv4). -Tim Shepard shep@alum.mit.edu _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Fri Jun 02 10:11:32 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FmAN8-0001Tu-S7; Fri, 02 Jun 2006 10:11:30 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FmAN8-0001Tm-3I; Fri, 02 Jun 2006 10:11:30 -0400 Received: from dsl092-066-146.bos1.dsl.speakeasy.net ([66.92.66.146] helo=alva.home) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FmAN6-0001k8-RS; Fri, 02 Jun 2006 10:11:30 -0400 Received: from shep (helo=alva.home) by alva.home with local-esmtp (Exim 3.36 #1 (Debian)) id 1FmAN3-0004OP-00; Fri, 02 Jun 2006 10:11:25 -0400 From: Tim Shepard To: Julien Laganier Subject: Re: [Hipsec] Storing ORCHIDs/HITs under a /28 In-reply-to: Your message of Fri, 02 Jun 2006 16:05:25 +0200. <200606021605.26291.julien.IETF@laposte.net> Date: Fri, 02 Jun 2006 10:11:25 -0400 Message-Id: X-Spam-Score: 0.1 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Cc: HIP , hipsec@lists.ietf.org, Pekka Nikander 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: , Errors-To: hipsec-bounces@lists.ietf.org > We'd like this allocation to be made as an IETF experimental > allocation performed by the IANA. IANA has a /23 allocated for that > purpose, so our prefix has to be strictly longer than 23, or more (We > cannot reasonably ask for say half of the available space.) > > Given that, 28 seemed sensible. > > Remember that this is an experimental prefix allocation. If the > experiment is successfull we might be able to request for a larger > allocation later on. This explanation helps much. Thanks. Sometimes experiments escape the laboratory and get popular faster than the experimental version can be replaced with a version designed to scale for the real world (e.g. IPv4). -Tim Shepard shep@alum.mit.edu _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Fri Jun 02 10:11:32 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FmAN9-0001Tz-0R; Fri, 02 Jun 2006 10:11:31 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FmAN8-0001Tm-3I; Fri, 02 Jun 2006 10:11:30 -0400 Received: from dsl092-066-146.bos1.dsl.speakeasy.net ([66.92.66.146] helo=alva.home) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FmAN6-0001k8-RS; Fri, 02 Jun 2006 10:11:30 -0400 Received: from shep (helo=alva.home) by alva.home with local-esmtp (Exim 3.36 #1 (Debian)) id 1FmAN3-0004OP-00; Fri, 02 Jun 2006 10:11:25 -0400 From: Tim Shepard To: Julien Laganier Subject: Re: [Hipsec] Storing ORCHIDs/HITs under a /28 In-reply-to: Your message of Fri, 02 Jun 2006 16:05:25 +0200. <200606021605.26291.julien.IETF@laposte.net> Date: Fri, 02 Jun 2006 10:11:25 -0400 Message-Id: X-Spam-Score: 0.1 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Cc: HIP , hipsec@lists.ietf.org, Pekka Nikander 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: , Errors-To: hipsec-bounces@lists.ietf.org > We'd like this allocation to be made as an IETF experimental > allocation performed by the IANA. IANA has a /23 allocated for that > purpose, so our prefix has to be strictly longer than 23, or more (We > cannot reasonably ask for say half of the available space.) > > Given that, 28 seemed sensible. > > Remember that this is an experimental prefix allocation. If the > experiment is successfull we might be able to request for a larger > allocation later on. This explanation helps much. Thanks. Sometimes experiments escape the laboratory and get popular faster than the experimental version can be replaced with a version designed to scale for the real world (e.g. IPv4). -Tim Shepard shep@alum.mit.edu _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Fri Jun 02 14:25:50 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FmELB-0004dJ-Mb; Fri, 02 Jun 2006 14:25:45 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FmELB-0004ch-1b for hipsec@ietf.org; Fri, 02 Jun 2006 14:25:45 -0400 Received: from av10-1-sn2.hy.skanova.net ([81.228.8.181]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FmEFh-0003c9-5T for hipsec@ietf.org; Fri, 02 Jun 2006 14:20:08 -0400 Received: by av10-1-sn2.hy.skanova.net (Postfix, from userid 502) id 5B67E389A8; Fri, 2 Jun 2006 20:20:03 +0200 (CEST) Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net [81.228.8.93]) by av10-1-sn2.hy.skanova.net (Postfix) with ESMTP id D7D5537FC5; Fri, 2 Jun 2006 20:20:03 +0200 (CEST) Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com [81.232.110.214]) by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id 88A7A37E43; Fri, 2 Jun 2006 20:20:03 +0200 (CEST) Received: from localhost ([127.0.0.1]) by shiraz.levkowetz.com with esmtp (Exim 4.62) (envelope-from ) id 1FmEFd-0002Qo-Ph; Fri, 02 Jun 2006 20:20:02 +0200 Message-ID: <44808151.50002@levkowetz.com> Date: Fri, 02 Jun 2006 20:20:01 +0200 From: Henrik Levkowetz User-Agent: Thunderbird 1.5.0.2 (Macintosh/20060308) MIME-Version: 1.0 To: Tim Shepard Subject: OT: One-in-a-million chances (Was: Re: [Hipsec] Storing ORCHIDs/HITs under a /28) References: In-Reply-To: X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: henrik@levkowetz.com X-SA-Exim-Scanned: No (on shiraz.levkowetz.com); SAEximRunCond expanded to false X-Spam-Score: 0.1 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Cc: HIP , Pekka Nikander , 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: , Errors-To: hipsec-bounces@lists.ietf.org > (How many random 100-bit strings have to be generated before the > probability of a duplication has crossed over the one-in-a-million > threshold? I'll try to estimate this sometime this weekend.) Avid Terry Pratchett readers will know that one-in-a-million chances come true nine times out of ten ,,,;-) Henrik _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Fri Jun 02 15:07:16 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FmEzL-00033W-7d; Fri, 02 Jun 2006 15:07:15 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FmEzJ-00033Q-R4 for hipsec@ietf.org; Fri, 02 Jun 2006 15:07:13 -0400 Received: from mailgw4.ericsson.se ([193.180.251.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FmEzH-0007vb-Up for hipsec@ietf.org; Fri, 02 Jun 2006 15:07:13 -0400 Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 945B4D92; Fri, 2 Jun 2006 21:07:10 +0200 (CEST) Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 2 Jun 2006 21:07:10 +0200 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 2 Jun 2006 21:07:10 +0200 Received: from [131.160.126.43] (rvi2-126-43.lmf.ericsson.se [131.160.126.43]) by mail.lmf.ericsson.se (Postfix) with ESMTP id DB0EE2403; Fri, 2 Jun 2006 22:07:09 +0300 (EEST) Message-ID: <44808C5D.8050908@ericsson.com> Date: Fri, 02 Jun 2006 22:07:09 +0300 From: Gonzalo Camarillo User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Julien Laganier References: <200606021428.18306.julien.IETF@laposte.net> In-Reply-To: <200606021428.18306.julien.IETF@laposte.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 02 Jun 2006 19:07:10.0142 (UTC) FILETIME=[BFA96DE0:01C68677] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Cc: HIP , Pekka Nikander Subject: [Hipsec] Re: Storing ORCHIDs/HITs under a /28 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: , Errors-To: hipsec-bounces@lists.ietf.org Hi, just to be sure, if nobody screams before Friday June 9th on this mailing list, we are going to move forward with the /28 allocation. As soon as we resolve this, we will request the publication of the base spec and the esp draft. Shortly after that, we will request the publication of the rest of our current drafts, recharter, and start working officially on the new items. Cheers, Gonzalo Julien Laganier wrote: > Folks, > > The proposed ORCHID prefix length of 8-bits has been discussed on both > HIPsec and int-area ML. Some persons have objected that allocation > because they believe an 8-bits prefix is too short by some. We had an > offline discussion in the hope to find a solution acceptable for both > parties, and we eventually agreed that allocation of a /28 is the way > to move forward. > > Therefore, I'd like to confirm with the HIP WG that storing ORCHIDs > (hence HITs) under a /28 prefix is acceptable. The implication is > that the public key hash would be truncated to 100-bits. > > If you agree or disagree with that proposal, please say so ASAP (say > before next Friday, the 9th) so we can move forward and resubmit the > ORCHID draft before the cut-off. > > Thanks, > > --julien _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Tue Jun 06 08:56:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fnb6h-0006dU-TA; Tue, 06 Jun 2006 08:56:27 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fnb6g-0006Zo-Id for hipsec@ietf.org; Tue, 06 Jun 2006 08:56:26 -0400 Received: from ihug-mail.icp-qv1-irony6.iinet.net.au ([203.59.1.224] helo=mail-ihug.icp-qv1-irony6.iinet.net.au) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fnb6f-0005kH-1c for hipsec@ietf.org; Tue, 06 Jun 2006 08:56:26 -0400 Received: from 203-214-99-121.dyn.iinet.net.au (HELO T40) ([203.214.99.121]) by mail-ihug.icp-qv1-irony6.iinet.net.au with ESMTP; 06 Jun 2006 20:56:18 +0800 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="4.05,214,1146412800"; d="scan'208,217"; a="326646213:sNHT1554153402" From: "Joseph" To: Date: Tue, 6 Jun 2006 22:56:02 +1000 Message-ID: <000301c68968$97edb560$1800230a@T40> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcaJaJCJ8dUW5xkqT+682txk84sXQg== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-Spam-Score: 0.0 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Cc: Subject: [Hipsec] Question Related ESP and SPI 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="===============0617414796==" Errors-To: hipsec-bounces@lists.ietf.org This is a multi-part message in MIME format. --===============0617414796== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0004_01C689BC.6999C560" This is a multi-part message in MIME format. ------=_NextPart_000_0004_01C689BC.6999C560 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Dear All, I try to understand the ESP mode of HIP in deep. I know that the SA is based on the . The HIP packet is [IP Header | IPSec Header | IPSec Payload]. The host will decrypt the IPSec Payload and then replace the IP address by HIT. I want to know, before decryption, can the host know if HIT of destination and the source? If yes, how? Thanks a lot. Joseph ------=_NextPart_000_0004_01C689BC.6999C560 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable
Dear = All,
    I try to=20 understand the ESP mode of HIP in deep.  I know that the SA is = based on the=20 <Dest of HIT, SPI>. The HIP packet is [IP Header | IPSec Header | = IPSec=20 Payload]. The host will decrypt the IPSec Payload and then replace the = IP=20 address by HIT. I want to know, before decryption, can the host know = if HIT=20 of destination and the source? If yes, how?
    Thanks=20 a lot.
Joseph 
------=_NextPart_000_0004_01C689BC.6999C560-- --===============0617414796== 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 --===============0617414796==-- From hipsec-bounces@lists.ietf.org Wed Jun 07 02:35:32 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fnrda-0004Bb-UT; Wed, 07 Jun 2006 02:35:30 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FnrdY-0004BW-SM for hipsec@ietf.org; Wed, 07 Jun 2006 02:35:28 -0400 Received: from twilight.cs.hut.fi ([130.233.40.5]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FnrdX-0001QI-CI for hipsec@ietf.org; Wed, 07 Jun 2006 02:35:28 -0400 Received: by twilight.cs.hut.fi (Postfix, from userid 60001) id 81AAC323D; Wed, 7 Jun 2006 09:35:26 +0300 (EEST) X-Spam-Checker-Version: SpamAssassin 3.1.2-niksula20060321 (2006-05-25) on twilight.cs.hut.fi X-Spam-Level: X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.1.2-niksula20060321 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 170533215; Wed, 7 Jun 2006 09:35:26 +0300 (EEST) Received: from localhost (mkomu@localhost) by kekkonen.cs.hut.fi (8.13.4+Sun/8.13.3/Submit) with ESMTP id k576ZPhd003554; Wed, 7 Jun 2006 09:35:25 +0300 (EEST) X-Authentication-Warning: kekkonen.cs.hut.fi: mkomu owned process doing -bs Date: Wed, 7 Jun 2006 09:35:24 +0300 (EEST) From: Miika Komu X-X-Sender: mkomu@kekkonen.cs.hut.fi To: Joseph Subject: Re: [Hipsec] Question Related ESP and SPI In-Reply-To: <000301c68968$97edb560$1800230a@T40> Message-ID: References: <000301c68968$97edb560$1800230a@T40> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 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: , Errors-To: hipsec-bounces@lists.ietf.org On Tue, 6 Jun 2006, Joseph wrote: > I try to understand the ESP mode of HIP in deep. I know that the SA > is based on the . Well, only the SPI should really matter, but at least on linux is still used for matching. > The HIP packet is [IP Header | IPSec Header | IPSec Payload]. The host > will decrypt the IPSec Payload and then replace the IP address by HIT. I > want to know, before decryption, can the host know if HIT of destination > and the source? If yes, how? It is possible to trace the SPI to the corresponding HIT. The exact "how" details are implementation dependent. P.S. In BEET mode, the inner header (with HITs) is not included on wire. -- 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 Wed Jun 07 15:50:39 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fo434-00035H-Qk; Wed, 07 Jun 2006 15:50:38 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fo42X-000274-6N; Wed, 07 Jun 2006 15:50:05 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fo42X-0007YO-49; Wed, 07 Jun 2006 15:50:05 -0400 Received: from chsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.24.129] helo=oak.neustar.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Fo42U-0004SL-5A; Wed, 07 Jun 2006 15:50:04 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by oak.neustar.com (8.12.8/8.12.8) with ESMTP id k57Jo1WR007965 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Jun 2006 19:50:01 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Fo42T-0002jb-RV; Wed, 07 Jun 2006 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: Wed, 07 Jun 2006 15:50:01 -0400 X-Spam-Score: -5.9 (-----) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: hipsec@ietf.org Subject: [Hipsec] I-D ACTION:draft-ietf-hip-rvs-05.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: , 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-05.txt Pages : 15 Date : 2006-6-7 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-05.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-05.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-05.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: <2006-6-7120315.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-hip-rvs-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-hip-rvs-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-6-7120315.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 Wed Jun 07 16:37:22 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fo4mG-0006Fq-1M; Wed, 07 Jun 2006 16:37:20 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fo4mE-00061R-6k; Wed, 07 Jun 2006 16:37:18 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fo4Xi-0004r2-Jz; Wed, 07 Jun 2006 16:22:18 -0400 Received: from cypress.neustar.com ([209.173.57.84]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Fo4IT-0006FK-Fw; Wed, 07 Jun 2006 16:06:34 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by cypress.neustar.com (8.12.8/8.12.8) with ESMTP id k57Jo1mU017615 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 7 Jun 2006 19:50:02 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Fo42T-0002jR-Q9; Wed, 07 Jun 2006 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: Wed, 07 Jun 2006 15:50:01 -0400 X-Spam-Score: -2.6 (--) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Cc: hipsec@ietf.org Subject: [Hipsec] I-D ACTION:draft-ietf-hip-registration-02.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: , 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) Registration Extension Author(s) : J. Laganier, et al. Filename : draft-ietf-hip-registration-02.txt Pages : 14 Date : 2006-6-7 This document specifies a registration mechanism for the Host Identity Protocol (HIP) that allows hosts to register with services, such as HIP rendezvous servers or middleboxes. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hip-registration-02.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-registration-02.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-registration-02.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: <2006-6-7120115.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-hip-registration-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-hip-registration-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-6-7120115.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 Jun 08 04:05:42 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FoFWN-0008Lf-Ek; Thu, 08 Jun 2006 04:05:39 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FoFWL-0008La-Rd for hipsec@ietf.org; Thu, 08 Jun 2006 04:05:37 -0400 Received: from kyoto.netlab.nec.de ([195.37.70.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FoFWK-0000Xf-Bl for hipsec@ietf.org; Thu, 08 Jun 2006 04:05:37 -0400 Received: from lars.local (unknown [195.37.70.152]) by kyoto.netlab.nec.de (Postfix) with ESMTP id 3FE131BAC4D for ; Thu, 8 Jun 2006 09:55:18 +0200 (CEST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by lars.local (Postfix) with ESMTP id 0DD9310A403 for ; Thu, 8 Jun 2006 10:05:22 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v750) To: hipsec@ietf.org Message-Id: <41C187EF-CFA3-4D96-B5D0-E34353251C33@netlab.nec.de> From: Lars Eggert Date: Thu, 8 Jun 2006 10:05:20 +0200 X-Mailer: Apple Mail (2.750) X-Spam-Score: 0.0 (/) X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86 Cc: Subject: [Hipsec] rvs and registration drafts 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="===============1567408511==" Errors-To: hipsec-bounces@lists.ietf.org --===============1567408511== Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-73--351970717; protocol="application/pkcs7-signature" --Apple-Mail-73--351970717 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Hi, FYI, we resubmitted the rvs and registration drafts because they had timed out or were about to time out. No changes to the content compared to the old versions. Lars -- Lars Eggert NEC Network Laboratories --Apple-Mail-73--351970717 Content-Transfer-Encoding: base64 Content-Type: application/pkcs7-signature; name=smime.p7s Content-Disposition: attachment; filename=smime.p7s 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 hkiG9w0BCQUxDxcNMDYwNjA4MDgwNTIxWjAjBgkqhkiG9w0BCQQxFgQUMF9UYyDeyJNzo5iUhHsA 0IrjWOYwgdYGCSsGAQQBgjcQBDGByDCBxTCBvzELMAkGA1UEBhMCREUxHDAaBgNVBAgUE0JhZGVu LVfDdWVydHRlbWJlcmcxEzARBgNVBAcTCkhlaWRlbGJlcmcxFzAVBgNVBAoTDk5FQyBFdXJvcGUg THRkMR0wGwYDVQQLExROZXR3b3JrIExhYm9yYXRvcmllczEbMBkGA1UEAxMSa29iZS5uZXRsYWIu bmVjLmRlMSgwJgYJKoZIhvcNAQkBFhlsYXJzLmVnZ2VydEBuZXRsYWIubmVjLmRlAgEAMIHYBgsq hkiG9w0BCRACCzGByKCBxTCBvzELMAkGA1UEBhMCREUxHDAaBgNVBAgUE0JhZGVuLVfDdWVydHRl bWJlcmcxEzARBgNVBAcTCkhlaWRlbGJlcmcxFzAVBgNVBAoTDk5FQyBFdXJvcGUgTHRkMR0wGwYD VQQLExROZXR3b3JrIExhYm9yYXRvcmllczEbMBkGA1UEAxMSa29iZS5uZXRsYWIubmVjLmRlMSgw JgYJKoZIhvcNAQkBFhlsYXJzLmVnZ2VydEBuZXRsYWIubmVjLmRlAgEAMA0GCSqGSIb3DQEBAQUA BIIBAC5VNQwcDfoBkl5ZP8caNeQEYh7ZhMF3r8w4suSCQtl+YvDNgFrUFLs6dNDI8u4zLJN8AgQO 5xDHFBHU/bGwbnlE+yG9K3YHtT+kS9ioipbn0ytM3JSHPsg01hxZYFReTdF5GIDG9til+wbqa56n HcB5w3/sO4/0dIqA7EAEUfACFUuPFR0B2zejB7/ING6CJUgqpFpzrDuScBNN+5CktGpdC9a4RBZr UdalFSPiAjgIHSIr5bM/x6sQjFNRrz2pk1dQGQd07rbbT0X13FUC1u4x7uELW3A4bplnoT8/WfkZ KrR+nvc58Lwho6uR9nHA2YK/+0Fb15Co4sdmsIM7qzsAAAAAAAA= --Apple-Mail-73--351970717-- --===============1567408511== 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 --===============1567408511==-- From hipsec-bounces@lists.ietf.org Wed Jun 14 02:03:33 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FqOTS-0002g9-RQ; Wed, 14 Jun 2006 02:03:30 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FqOTR-0002g4-DJ for hipsec@ietf.org; Wed, 14 Jun 2006 02:03:29 -0400 Received: from twilight.cs.hut.fi ([130.233.40.5]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FqOTQ-0000av-2G for hipsec@ietf.org; Wed, 14 Jun 2006 02:03:29 -0400 Received: by twilight.cs.hut.fi (Postfix, from userid 60001) id 68621309E; Wed, 14 Jun 2006 09:03:27 +0300 (EEST) X-Spam-Checker-Version: SpamAssassin 3.1.2-niksula20060321 (2006-05-25) on twilight.cs.hut.fi X-Spam-Level: X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.1.2-niksula20060321 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 C33802EC7; Wed, 14 Jun 2006 09:03:26 +0300 (EEST) Received: from localhost (mkomu@localhost) by kekkonen.cs.hut.fi (8.13.4+Sun/8.13.3/Submit) with ESMTP id k5E63Npm009621; Wed, 14 Jun 2006 09:03:26 +0300 (EEST) X-Authentication-Warning: kekkonen.cs.hut.fi: mkomu owned process doing -bs Date: Wed, 14 Jun 2006 09:03:23 +0300 (EEST) From: Miika Komu X-X-Sender: mkomu@kekkonen.cs.hut.fi To: hipsec@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Cc: hipsec-rg@listserv.cybertrust.com Subject: [Hipsec] HIP NAT traversal 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: , Errors-To: hipsec-bounces@lists.ietf.org Message: 5 Date: Tue, 13 Jun 2006 18:50:01 -0400 From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-schmitt-hip-nat-traversal-01.txt To: i-d-announce@ietf.org Message-ID: Content-Type: text/plain; charset="us-ascii" A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : HIP Extensions for the Traversal of Network Address Translators Author(s) : V. Schmitt, et al. Filename : draft-schmitt-hip-nat-traversal-01.txt Pages : 33 Date : 2006-6-13 This document specifies extensions to Host Identity Protocol (HIP) to support traversal of Network Address Translator (NAT) middleboxes. The traversal mechanism tunnels HIP control and data traffic over UDP and enables HIP initiators which MAY be behind NATs to contact HIP responders which MAY be behind another NAT. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-schmitt-hip-nat-traversal-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. -- 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 Fri Jun 16 03:13:37 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fr8WN-0006IW-ML; Fri, 16 Jun 2006 03:13:35 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fr8WL-0006IR-9p for hipsec@ietf.org; Fri, 16 Jun 2006 03:13:33 -0400 Received: from n2.nomadiclab.com ([193.234.219.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fr8WK-0000bB-0K for hipsec@ietf.org; Fri, 16 Jun 2006 03:13:33 -0400 Received: from n2.nomadiclab.com (localhost [127.0.0.1]) by n2.nomadiclab.com (Postfix) with ESMTP id 5468E212C5D for ; Fri, 16 Jun 2006 10:13:31 +0300 (EEST) Received: from [193.234.219.125] (n125.nomadiclab.com [193.234.219.125]) by n2.nomadiclab.com (Postfix) with ESMTP id E570B212C4A for ; Fri, 16 Jun 2006 10:13:30 +0300 (EEST) Message-ID: <44925A1A.6000609@nomadiclab.com> Date: Fri, 16 Jun 2006 10:13:30 +0300 From: Petri Jokela User-Agent: Thunderbird 1.5 (X11/20051201) MIME-Version: 1.0 To: HIP Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Cc: Subject: [Hipsec] HIP Base & ESP drafts 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: , Errors-To: hipsec-bounces@lists.ietf.org Folks, I submitted yesterday HIP base (06) and HIP ESP (03) versions. You can find those versions (+ diffs from previous ones) from: http://hip4inter.net/drafts.php BR, Petri _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Fri Jun 16 15:50:34 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FrKKt-0008N9-Pq; Fri, 16 Jun 2006 15:50:32 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FrKKS-0007Yv-68; Fri, 16 Jun 2006 15:50:04 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FrKKS-0000fJ-3u; Fri, 16 Jun 2006 15:50:04 -0400 Received: from pine.neustar.com ([209.173.57.70]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FrKKQ-0007on-LP; Fri, 16 Jun 2006 15:50:04 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by pine.neustar.com (8.12.8/8.12.8) with ESMTP id k5GJo2Hp024926 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 16 Jun 2006 19:50:02 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1FrKKQ-0004s5-4L; Fri, 16 Jun 2006 15:50:02 -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: Fri, 16 Jun 2006 15:50:02 -0400 X-Spam-Score: -2.6 (--) X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1 Cc: hipsec@ietf.org Subject: [Hipsec] I-D ACTION:draft-ietf-hip-base-06.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: , 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-06.txt Pages : 102 Date : 2006-6-16 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-06.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-06.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-06.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: <2006-6-16140522.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-hip-base-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-hip-base-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-6-16140522.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 Jun 16 18:11:23 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FrMXB-0006J5-LD; Fri, 16 Jun 2006 18:11:21 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FrMXA-0006GJ-41; Fri, 16 Jun 2006 18:11:20 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FrL6y-0007Bj-PU; Fri, 16 Jun 2006 16:40:12 -0400 Received: from cypress.neustar.com ([209.173.57.84]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FrKLO-0007sp-Kl; Fri, 16 Jun 2006 15:51:05 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by cypress.neustar.com (8.12.8/8.12.8) with ESMTP id k5GJo2mU027290 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 16 Jun 2006 19:50:02 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1FrKKQ-0004s8-57; Fri, 16 Jun 2006 15:50:02 -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: Fri, 16 Jun 2006 15:50:02 -0400 X-Spam-Score: -2.6 (--) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Cc: hipsec@ietf.org Subject: [Hipsec] I-D ACTION:draft-ietf-hip-esp-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: , 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-03.txt Pages : 33 Date : 2006-6-16 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-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-esp-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-esp-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: <2006-6-16140659.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-hip-esp-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-hip-esp-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-6-16140659.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 Jun 19 12:01:25 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FsMBo-0002Wr-BR; Mon, 19 Jun 2006 12:01:24 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FsMBm-0002Wi-Sm for hipsec@ietf.org; Mon, 19 Jun 2006 12:01:22 -0400 Received: from mh1.eu.ntt.net ([212.119.0.10]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FsMBl-0007h0-Cr for hipsec@ietf.org; Mon, 19 Jun 2006 12:01:22 -0400 Received: (qmail 29649 invoked by uid 2101); 19 Jun 2006 17:01:20 +0100 Received: from julien.IETF@laposte.net by mh1 by uid 0 with qmail-scanner-1.22st (clamdscan: 0.85.1. spamassassin: 3.0.4. perlscan: 1.22st. Clear:RC:1(212.119.9.178):. Processed in 0.024201 secs); 19 Jun 2006 16:01:20 -0000 Received: from unknown (HELO ?192.168.1.117?) (212.119.9.178) by mx1.eu.ntt.net with SMTP; 19 Jun 2006 17:01:20 +0100 From: Julien Laganier To: hipsec@ietf.org, Internet Area Date: Mon, 19 Jun 2006 18:01:27 +0200 User-Agent: KMail/1.8.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200606191801.27634.julien.IETF@laposte.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Cc: Subject: [Hipsec] Updated ORCHID 28-bits prefix draft 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: , Errors-To: hipsec-bounces@lists.ietf.org Folks, I will submit an updated ORCHID draft asking allocation of a 28-bits prefix out of the IPv6 IANA Special Purpose Address Block. Until it shows up in the I-D repository it's available there: Htmlized wdiff from previous version is also there: --julien _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Tue Jun 20 07:41:28 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fsebk-0001Pi-0O; Tue, 20 Jun 2006 07:41:24 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fsebj-0001PK-FM; Tue, 20 Jun 2006 07:41:23 -0400 Received: from twilight.cs.hut.fi ([130.233.40.5]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fsebh-00052e-4d; Tue, 20 Jun 2006 07:41:23 -0400 Received: by twilight.cs.hut.fi (Postfix, from userid 60001) id 5EA892EEA; Tue, 20 Jun 2006 14:41:20 +0300 (EEST) X-Spam-Checker-Version: SpamAssassin 3.1.2-niksula20060321 (2006-05-25) on twilight.cs.hut.fi X-Spam-Level: X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.1.2-niksula20060321 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 DAC6C2EE7; Tue, 20 Jun 2006 14:41:19 +0300 (EEST) Received: from localhost (mkomu@localhost) by kekkonen.cs.hut.fi (8.13.4+Sun/8.13.3/Submit) with ESMTP id k5KBfJ4x019765; Tue, 20 Jun 2006 14:41:19 +0300 (EEST) X-Authentication-Warning: kekkonen.cs.hut.fi: mkomu owned process doing -bs Date: Tue, 20 Jun 2006 14:41:18 +0300 (EEST) From: Miika Komu X-X-Sender: mkomu@kekkonen.cs.hut.fi To: hipsec@ietf.org, shim6@psg.com, multimobsec-api@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Cc: Subject: [Hipsec] multihoming API draft for SHIM6/HIP 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: , Errors-To: hipsec-bounces@lists.ietf.org A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Socket Application Program Interface (API) for Multihoming Shim Author(s) : M. Komu, et al. Filename : draft-sugimoto-multihome-shim-api-00.txt Pages : 30 Date : 2006-6-19 This document specifies a socket API for the multihoming shim layer. The API aims to enable interactions between the applications and the multihoming shim layer for advanced locator management and also for accessing to information about failure detection and path exploration. This document is based on an assumption that a multhomed host is equipped with a 'shim' layer which essentially maintains mappings between identifiers and locators at the IP layer. SHIM6 and HIP are examples of this shim layer. Hence, the API can be commonly used by SHIM6 and HIP. We created another mailing list to avoid excessive cross-posting: https://www1.ietf.org/mailman/listinfo/multimobsec-api -- Miika Komu 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 Thu Jun 22 14:39:07 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtU53-0007qT-3l; Thu, 22 Jun 2006 14:39:05 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FtU51-0007nv-7p; Thu, 22 Jun 2006 14:39:03 -0400 Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FtP7M-0003R6-Ow; Thu, 22 Jun 2006 09:21:08 -0400 Received: from smtp02.uc3m.es ([163.117.136.122]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FtOy0-0004S0-F3; Thu, 22 Jun 2006 09:11:30 -0400 Received: from smtp02.uc3m.es (localhost [127.0.0.1]) by localhost.uc3m.es (Postfix) with ESMTP id 27A6695EB4; Thu, 22 Jun 2006 15:11:25 +0200 (CEST) Received: from [163.117.203.126] (unknown [163.117.203.126]) by smtp02.uc3m.es (Postfix) with ESMTP id 9F6F195F37; Thu, 22 Jun 2006 15:11:24 +0200 (CEST) In-Reply-To: <200606191801.27634.julien.IETF@laposte.net> References: <200606191801.27634.julien.IETF@laposte.net> Mime-Version: 1.0 (Apple Message framework v624) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: quoted-printable From: marcelo bagnulo braun Date: Thu, 22 Jun 2006 16:11:23 +0300 To: Julien Laganier X-Mailer: Apple Mail (2.624) X-Spam-Score: -2.5 (--) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Cc: hipsec@ietf.org, Internet Area Subject: [Hipsec] Re: [Int-area] Updated ORCHID 28-bits prefix draft 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: , Errors-To: hipsec-bounces@lists.ietf.org Hi, i think 100 bits for hash is a reasonable tradeoff for this. Regards, marcelo El 19/06/2006, a las 19:01, Julien Laganier escribi=F3: > Folks, > > I will submit an updated ORCHID draft asking allocation of a 28-bits > prefix out of the IPv6 IANA Special Purpose Address Block. > > Until it shows up in the I-D repository it's available there: > > > > Htmlized wdiff from previous version is also there: > > -01.html> > > --julien > > _______________________________________________ > Int-area mailing list > Int-area@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/int-area > _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec From hipsec-bounces@lists.ietf.org Mon Jun 26 05:21:51 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FunHx-0006xF-Ed; Mon, 26 Jun 2006 05:21:49 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FunHI-0006RL-DL; Mon, 26 Jun 2006 05:21:08 -0400 Received: from twilight.cs.hut.fi ([130.233.40.5]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FunCt-00039w-Qs; Mon, 26 Jun 2006 05:16:38 -0400 Received: by twilight.cs.hut.fi (Postfix, from userid 60001) id DD1493279; Mon, 26 Jun 2006 12:16:34 +0300 (EEST) X-Spam-Checker-Version: SpamAssassin 3.1.2-niksula20060321 (2006-05-25) on twilight.cs.hut.fi X-Spam-Level: X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.1.2-niksula20060321 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 EE77930B3; Mon, 26 Jun 2006 12:16:33 +0300 (EEST) Received: from localhost (mkomu@localhost) by kekkonen.cs.hut.fi (8.13.4+Sun/8.13.3/Submit) with ESMTP id k5Q9GX4M029288; Mon, 26 Jun 2006 12:16:33 +0300 (EEST) X-Authentication-Warning: kekkonen.cs.hut.fi: mkomu owned process doing -bs Date: Mon, 26 Jun 2006 12:16:32 +0300 (EEST) From: Miika Komu X-X-Sender: mkomu@kekkonen.cs.hut.fi To: hipsec@ietf.org, multimobsec-api@ietf.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Cc: shim6@psg.com Subject: [Hipsec] Native SHIM APIs 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: , Errors-To: hipsec-bounces@lists.ietf.org A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Native Application Programming Interfaces for SHIM Layer Prococols Author(s) : M. Komu Filename : draft-komu-shim-native-api-00.txt Pages : 21 Date : 2006-6-22 This document proposes extensions to the current networking APIs for protocols based on identifier/locator split. Currently, the document focuses on HIP, but the extensions can be used also by other protocols similar "shim" layer protocols. Using the API extensions, new SHIM aware applications can gain a better control of the SHIM layer and endpoint identifiers. For example, the applications can query and set SHIM related attributes, or specify their own endpoint identifiers for a host. In addition, a new indirection element called endpoint descriptor is defined for SHIM aware applications. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-komu-shim-native-api-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. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. There is a mailing list for the SHIM6/HIP related API discussion to reduce cross-posting: https://www1.ietf.org/mailman/listinfo/multimobsec-api -- Miika Komu 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 Jun 26 18:50:21 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FuzuN-0004oX-0S; Mon, 26 Jun 2006 18:50:19 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fuzu6-0004OZ-LH; Mon, 26 Jun 2006 18:50:02 -0400 Received: from willow.neustar.com ([209.173.53.84]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fuzu6-0007eE-2p; Mon, 26 Jun 2006 18:50:02 -0400 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by willow.neustar.com (8.12.8/8.12.8) with ESMTP id k5QMo1Rx004074 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 26 Jun 2006 22:50:01 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1Fuzu5-0007zF-L3; Mon, 26 Jun 2006 18: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, 26 Jun 2006 18:50:01 -0400 X-Spam-Score: 0.3 (/) X-Scan-Signature: f66b12316365a3fe519e75911daf28a8 Cc: hipsec@ietf.org Subject: [Hipsec] I-D ACTION:draft-ietf-hip-mm-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: , 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 : End-Host Mobility and Multihoming with the Host Identity Protocol Author(s) : P. Nikander Filename : draft-ietf-hip-mm-04.txt Pages : 47 Date : 2006-6-26 This document defines mobility and multihoming extensions to the Host Identity Protocol (HIP). Specifically, this document defines a general "LOCATOR" parameter for HIP messages that allows for a HIP host to notify peers about alternate addresses at which it may be reached. This document also defines elements of procedure for mobility of a HIP host-- the process by which a host dynamically changes the primary locator that it uses to receive packets. While the same LOCATOR parameter can also be used to support end-host multihoming, detailed procedures are left for further study. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-hip-mm-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-mm-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-mm-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: <2006-6-26161509.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-hip-mm-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-hip-mm-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-6-26161509.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 Jun 30 07:44:58 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FwHQd-0007di-3n; Fri, 30 Jun 2006 07:44:55 -0400 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FwHQb-0007dd-TZ for hipsec@ietf.org; Fri, 30 Jun 2006 07:44:53 -0400 Received: from mailgw4.ericsson.se ([193.180.251.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FwHQZ-0006BQ-Bn for hipsec@ietf.org; Fri, 30 Jun 2006 07:44:53 -0400 Received: from esealmw127.eemea.ericsson.se (unknown [153.88.254.122]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 615E5500003; Fri, 30 Jun 2006 13:44:18 +0200 (CEST) Received: from esealmw129.eemea.ericsson.se ([153.88.254.173]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 30 Jun 2006 13:44:15 +0200 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 30 Jun 2006 13:44:15 +0200 Received: from [131.160.126.23] (rvi2-126-23.lmf.ericsson.se [131.160.126.23]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 52111236B; Fri, 30 Jun 2006 14:44:15 +0300 (EEST) Message-ID: <44A50E8D.1060800@ericsson.com> Date: Fri, 30 Jun 2006 14:44:13 +0300 From: Gonzalo Camarillo User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: HIP Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 30 Jun 2006 11:44:15.0658 (UTC) FILETIME=[8399F8A0:01C69C3A] X-Brightmail-Tracker: AAAAAA== X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Cc: Subject: [Hipsec] HIP Draft Agenda 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: , Errors-To: hipsec-bounces@lists.ietf.org Folks, we have just uploaded a draft agenda for our session in Montreal. You can fetch it from: http://www3.ietf.org/proceedings/06jul/agenda/hip.html Note that we have only received one agenda request so far. If you have any other agenda request, you can still send it to us until Monday. Cheers, Gonzalo HIP co-chair _______________________________________________ Hipsec mailing list Hipsec@lists.ietf.org https://www1.ietf.org/mailman/listinfo/hipsec