From sidr-bounces@ietf.org Sun Mar 12 22:17:02 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FIdYK-0006ae-Ia; Sun, 12 Mar 2006 22:17:00 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FIdYJ-0006aX-5A
	for sidr@ietf.org; Sun, 12 Mar 2006 22:16:59 -0500
Received: from kahuna.telstra.net ([203.50.0.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FIdYH-0005TU-F4
	for sidr@ietf.org; Sun, 12 Mar 2006 22:16:59 -0500
Received: from gihm3.apnic.net (protege.telstra.net [203.50.0.194] (may be
	forged))
	by kahuna.telstra.net (8.12.11/8.12.11) with ESMTP id k2D3GhKY080664;
	Mon, 13 Mar 2006 14:16:44 +1100 (EST) (envelope-from gih@apnic.net)
Message-Id: <6.2.0.14.2.20060313140150.02ad1d28@kahuna.telstra.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14
Date: Mon, 13 Mar 2006 14:16:33 +1100
To: sidr@ietf.org
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <5.0.0.25.2.20060302150943.02d95a68@zircon.juniper.net>
References: <p06230905bfb4d325174d@[128.89.89.106]>
	<20051129132050.4e7421a9@garlic.apnic.net>
	<p06230905bfb4d325174d@[128.89.89.106]>
	<5.0.0.25.2.20060302150943.02d95a68@zircon.juniper.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: fenner@research.att.com
Subject: [Sidr] Agenda for SIDR Meeting
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sidr>,
	<mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sidr>,
	<mailto:sidr-request@ietf.org?subject=subscribe>
Errors-To: sidr-bounces@ietf.org

1510-1610 Afternoon Session II
Cortez AB     RTG    sidr      Secure Inter-domain Routing BOF

BOF Chair - Geoff Huston

Agenda

1. Agenda Bashing, Scribe Victimization

2. BOF Status Review
                 Chair

3. Briefing on a PKI proposal for IP resource certification
                 Steve Kent

4. Update on APNIC resource certification trial
                   Geoff Huston

5. Discussion

==============================================

I understand that approval of the SIDR charter is close to completion (or 
at least thats what I understand from reading the IESG minutes minutes of 
the 2nd Feb, so I've dropped further consideration of the proposaed charter 
form this agenda.

regards,

    Geoff




_______________________________________________
Sidr mailing list
Sidr@ietf.org
https://www1.ietf.org/mailman/listinfo/sidr



From sidr-bounces@ietf.org Thu Mar 23 08:54:36 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FMQGp-00021X-L6; Thu, 23 Mar 2006 08:54:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FMQGn-00021S-RA
	for sidr@ietf.org; Thu, 23 Mar 2006 08:54:33 -0500
Received: from kahuna.telstra.net ([203.50.0.6])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMQGm-00036J-4G
	for sidr@ietf.org; Thu, 23 Mar 2006 08:54:33 -0500
Received: from gihm3.apnic.net (kahuna.telstra.net [IPv6:2001:360::4])
	by kahuna.telstra.net (8.12.11/8.12.11) with ESMTP id k2NDsPQg054318;
	Fri, 24 Mar 2006 00:54:27 +1100 (EST) (envelope-from gih@apnic.net)
Message-Id: <6.2.0.14.2.20060324005247.02de6620@localhost>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14
Date: Fri, 24 Mar 2006 00:54:25 +1100
To: sidr@ietf.org
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <6.2.0.14.2.20060222211102.02be4f00@kahuna.telstra.net>
References: <6.2.0.14.2.20060222211102.02be4f00@kahuna.telstra.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027
Cc: fenner@research.att.com
Subject: [Sidr] SIDR BOF Minutes from IETF 65
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sidr>,
	<mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sidr>,
	<mailto:sidr-request@ietf.org?subject=subscribe>
Errors-To: sidr-bounces@ietf.org

SIDR BOF
WEDNESDAY, March 22 2006
1510-1610

BOF Chair - Geoff Huston

AGENDA

1. Agenda Bashing, Scribe Victimization


2. BOF Status Review
                 Chair


3. Briefing on a PKI proposal for IP resource certification
                 Steve Kent


4. Update on APNIC resource certification trial
                   Geoff Huston


5. Discussion


NOTES (Mark Andrews, Tony Tauber)

2. BOF Status Review

   2nd BOF.  IETF 64 featured extended charter discussion. The proposed SIDR
   Charter was submitted to the ADs in November 2005. Ross Callon (incoming
   AD) reported that the AD consideration of the proposed charter was close
   to completion and would be scheduled for IESG consideration in the near
   future. The advise to SIDR was to assume chartering and commence the work
   plan.

   This meeting has BOF-style presentations to describe motivation rather
   than specific work items.

3. Briefing on a PKI proposal for IP resource certification
                 Steve Kent

    [presentation]

    Jeff Schiller: How does the ROA structure operate when attempting to
    shift upstream providers?

         A: Request a time-limited ROA from old provider to allow the new
         provider to originate the old address during a transition.


      What happens when old provider doesn't co-operate?

         A: That is a business problem


    Pekka Savola: How are the early allocations dealt with?

         A: handled by IANA?  Need to be accommodated in some fashion, but
         this is not a direct question for SIDR.

    Eric Rescorla: Who will be the root? Could this have multiple roots?


         A: There may be a set of trust anchors, or a single trust anchor.
         This is a certificate validation question and the trust anchors are
         a matter for the relying parties to determine.


4. Update on APNIC resource certification trial
                   Geoff Huston

    [presentation]

         ftp://ftp.apnic.net/pub/test-certs/


    Pekka Savola: How is the public key handled?


         A: This is a trial of technology only.  There are no real client
         private keys, and the public / private key pairs are generated by
         the trial engine. Both keys are in the repository. This is not
         standard repository practice.


    Sandy Murphy: Software for handling certificates?


         A: George Michaelson: CPAN based, available rsn


    Sandy Murphy: What about the repository?


        A: Stephen Kent: the query from replying parties is not quite a case
        of "give me everything" and more likely one of "give me what has
        changed".  Start simple.


         A: George Michaelson: APNIC Trial repository is ~9 MB.  Largest
         Cert is 8k


    Steve Casner: Information update delay.  Will it be multiple days?


         A: Geoff Huston: CPS need to written.  Within RIR is business
         decision.




_______________________________________________
Sidr mailing list
Sidr@ietf.org
https://www1.ietf.org/mailman/listinfo/sidr



From sidr-bounces@ietf.org Fri Mar 24 16:41:28 2006
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1FMu27-0003xg-NV; Fri, 24 Mar 2006 16:41:23 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1FMu25-0003xb-Rn
	for sidr@ietf.org; Fri, 24 Mar 2006 16:41:21 -0500
Received: from postman.ripe.net ([193.0.0.199])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FMu25-0004RI-FY
	for sidr@ietf.org; Fri, 24 Mar 2006 16:41:21 -0500
Received: by postman.ripe.net (Postfix, from userid 4008)
	id 258462407C; Fri, 24 Mar 2006 22:41:21 +0100 (CET)
Received: from herring.ripe.net (herring.ripe.net [193.0.1.203])
	by postman.ripe.net (Postfix) with ESMTP id CE54F23F60;
	Fri, 24 Mar 2006 22:41:20 +0100 (CET)
Received: from Geir.ripe.net (cow.ripe.net [193.0.1.239])
	by herring.ripe.net (Postfix) with ESMTP id 433892F59E;
	Fri, 24 Mar 2006 22:41:20 +0100 (CET)
Message-Id: <7.0.1.0.2.20060324222959.0344ca40@ripe.net>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Fri, 24 Mar 2006 22:41:17 +0100
To: Geoff Huston <gih@apnic.net>, sidr@ietf.org
From: Henk Uijterwaal <henk@ripe.net>
Subject: [sidr] One potential work item.
In-Reply-To: <6.2.0.14.2.20060324005247.02de6620@localhost>
References: <6.2.0.14.2.20060222211102.02be4f00@kahuna.telstra.net>
	<6.2.0.14.2.20060324005247.02de6620@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-RIPE-Spam-Level: 
X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00
X-RIPE-Spam-Status: N 0.037186 / -4.4
X-RIPE-Signature: 80bedc68089a48acf5c0c295675abe67
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: fenner@research.att.com
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sidr>,
	<mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sidr>,
	<mailto:sidr-request@ietf.org?subject=subscribe>
Errors-To: sidr-bounces@ietf.org

All,

Since Geoff asked about work items for this group...

One thing that I'd find particularly useful, is a requirements document
for RIRs.   Assume that the RIRs will set up a PKI and hand out a (or more)
certificate(s) for each IP/AS allocation.

* Vendors/protocol designers
   = Requirements that will allow the certificates to be used with
     {s|so|ps|...}BGP.  I don't want to choose a protocol, but I do want
     to make sure that we don't force people into a certain direction
     before the various technologies are fully mature.
   = ...

* LIRs/ISPs
   = How do they see themselves use these certificates
   = What would make them useful/useless.
   = What happens if a block is transferred to a customer.
   = What happens if resources are exchanged (traded) between ISPs.
   = What should be common amongst all 5 RIRs.
   = Interaction with IRRs and such
   = Can they use certificates from other bodies, who controls their
     identity.
   = ...

* Government bodies:
   = Requirements on the PKI (EU, DHS, ...)
     (We will hand out certificates that are used world-wide, so we better
      make sure that they confirm to all relevant local regulations).
   = ...

* Other expected use cases

There is probably a lot more.  However, APNIC has set up a trial PKI,
RIPE NCC has a project in this direction, so we better document
requirements.

Henk



------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.net
RIPE Network Coordination Centre          http://www.amsterdamned.org/~henk
P.O.Box 10096          Singel 258         Phone: +31.20.5354414
1001 EB Amsterdam      1016 AB Amsterdam  Fax: +31.20.5354445
The Netherlands        The Netherlands    Mobile: +31.6.55861746
------------------------------------------------------------------------------

1160438400. Watch this space... 


_______________________________________________
Sidr mailing list
Sidr@ietf.org
https://www1.ietf.org/mailman/listinfo/sidr



