Re: [sidr] WGLC draft-sidr-rpki-rtr - take 2?

Hannes Gredler <hannes@juniper.net> Mon, 06 June 2011 11:03 UTC

Return-Path: <hannes@juniper.net>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9959D11E80F8 for <sidr@ietfa.amsl.com>; Mon, 6 Jun 2011 04:03:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r9EBy+XgYh8q for <sidr@ietfa.amsl.com>; Mon, 6 Jun 2011 04:03:03 -0700 (PDT)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by ietfa.amsl.com (Postfix) with ESMTP id 383F511E80D6 for <sidr@ietf.org>; Mon, 6 Jun 2011 04:03:02 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP ID DSNKTeyz4wf80OjfMjzm7qKCJmLQRae8Tnd3@postini.com; Mon, 06 Jun 2011 04:03:02 PDT
Received: from hannes-755.juniper.net (172.23.4.62) by P-EMHUB02-HQ.jnpr.net (172.24.192.33) with Microsoft SMTP Server id 8.2.254.0; Mon, 6 Jun 2011 04:00:35 -0700
Received: by hannes-755.juniper.net (Postfix, from userid 1000) id 2FA2028FD2; Mon, 6 Jun 2011 13:00:34 +0200 (CEST)
Date: Mon, 06 Jun 2011 13:00:34 +0200
From: Hannes Gredler <hannes@juniper.net>
To: Robert Raszuk <raszuk@cisco.com>
Message-ID: <20110606110032.GA3117@juniper.net>
References: <m21uzwr3tw.wl%randy@psg.com> <BANLkTimPnMfE1ii=6uwAckoFY0yUU=w43g@mail.gmail.com> <BANLkTinu8pxxCj4cdJzbS3z5h=8=s+U3Gw@mail.gmail.com> <D1D8138DDF34B34B8BC68A11262D10790F6233E006@EUSAACMS0701.eamcs.ericsson.se> <Pine.WNT.4.64.1106031624560.2148@SMURPHY-LT.columbia.ads.sparta.com> <D1D8138DDF34B34B8BC68A11262D10790F6233E04A@EUSAACMS0701.eamcs.ericsson.se> <m2aadwkdeu.wl%randy@psg.com> <4DEC0344.20407@cisco.com> <m2mxhvgwme.wl%randy@psg.com> <4DECB0DC.4000902@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4DECB0DC.4000902@cisco.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: sidr@ietf.org
Subject: Re: [sidr] WGLC draft-sidr-rpki-rtr - take 2?
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Jun 2011 11:03:03 -0000

On Mon, Jun 06, 2011 at 12:50:04PM +0200, Robert Raszuk wrote:
| If indeed requirement is to support decent authentication on wide
| spectrum of operating systems why not consider application level
| approach of SSL/TLS and leave the need for TCP kernel hacking alone
| ? rfc5246 ?
| 
| Routers support it today so would any unix flavor as it will come
| with the application if not already there.

hi robert,

---

quoting from rfc 5246:

   The primary goal of the TLS protocol is to provide privacy and data
                                              ^^^^^^^^^^^^^^^^^^^^^^^^
   integrity between two communicating applications.  The protocol is
   ^^^^^^^^^
   composed of two layers: the TLS Record Protocol and the TLS Handshake
   Protocol.  At the lowest level, layered on top of some reliable
   transport protocol (e.g., TCP [TCP]), is the TLS Record Protocol.
   The TLS Record Protocol provides connection security that has two
   basic properties:

---

we are just looking for a protocol which ensures data-integrity,
privacy is not of concern;

/hannes