IETF Logo Mail Archive

Re: [karp] Handling of LDP hello packets and the crypto table

Acee Lindem <acee.lindem@ericsson.com> Tue, 17 September 2013 22:35 UTC

Return-Path: <acee.lindem@ericsson.com>
X-Original-To: karp@ietfa.amsl.com
Delivered-To: karp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33E9911E8140 for <karp@ietfa.amsl.com>; Tue, 17 Sep 2013 15:35:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BR2T4rfcfxWi for <karp@ietfa.amsl.com>; Tue, 17 Sep 2013 15:34:57 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id AF05611E825E for <karp@ietf.org>; Tue, 17 Sep 2013 15:34:54 -0700 (PDT)
X-AuditID: c618062d-b7fda8e0000024c6-ef-5238d90d5894
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id E0.C6.09414.D09D8325; Wed, 18 Sep 2013 00:34:54 +0200 (CEST)
Received: from EUSAAMB101.ericsson.se ([147.117.188.118]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.02.0328.009; Tue, 17 Sep 2013 18:34:53 -0400
From: Acee Lindem <acee.lindem@ericsson.com>
To: Sam Hartman <hartmans-ietf@mit.edu>, "Joel M. Halpern" <jmh@joelhalpern.com>
Thread-Topic: [karp] Handling of LDP hello packets and the crypto table
Thread-Index: AQHOra+JHI5ZOVzUjE+8q62qULz8DZm+/VUAgAsVpf2AAEudgA==
Date: Tue, 17 Sep 2013 22:34:52 +0000
Message-ID: <94A203EA12AECE4BA92D42DBFFE0AE470305670B@eusaamb101.ericsson.se>
In-Reply-To: <tslbo3rfq50.fsf@mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.6.130613
x-originating-ip: [147.117.188.134]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3BD4F808800F104BA008CC398E10852F@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPLMWRmVeSWpSXmKPExsUyuXRPoC7fTYsgg4azLBZzvq5ms/h46g2T xd5vaxgdmD2WLPnJ5HFuyndGj6YzR5kDmKO4bFJSczLLUov07RK4MjYsXcdYcIej4vzGJ2wN jM3sXYycHBICJhJ3zrWyQthiEhfurWfrYuTiEBI4yijxcsMGKGc5o8Sb7evAOtgEdCSeP/rH DGKLCARJfHmxgBHEZhZQluhu6WABsYUF3CR+/jsAVeMuMenVVKBBHEC2k8THj0wgYRYBVYmt n1+B2bwCvhK9ja1g5ZwCahL3246AjWQEOuj7qTVMEOPFJW49mc8EcaiAxJI955khbFGJl4// gT0gKqAn0T1rOdQzyhJLnuxngejVkViw+xMbhG0tsbP9JTOErS2xbOFrZogbBCVOznzCMoFR fBaSdbOQtM9C0j4LSfssJO0LGFlXMXKUFqeW5aYbGWxiBEbaMQk23R2Me15aHmKU5mBREudd pXcmUEggPbEkNTs1tSC1KL6oNCe1+BAjEwenVAOjn9OZMwoVq9LWndFU+rGe89GsAP/TDI2W luZL2XabbnDdcdfzW9PzskkHi65L2NQ+PS2jOMP1Z88/bg7O4xxMDK6nuSVPLHr66DLDlydP Y4t1XBONjs2q/HLBxL9fOtPw9dZ/51epr5t54clUrvS+PYsVzu0/ki+2iFWAdxevApMNn6hl 1MP/SizFGYmGWsxFxYkAEomFKIICAAA=
Cc: "karp@ietf.org" <karp@ietf.org>
Subject: Re: [karp] Handling of LDP hello packets and the crypto table
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion list for key management for routing and transport protocols <karp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/karp>, <mailto:karp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/karp>
List-Post: <mailto:karp@ietf.org>
List-Help: <mailto:karp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/karp>, <mailto:karp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Sep 2013 22:35:11 -0000

Hi Sam, 

I don't necessarily agree that this one use case should greatly complicate
the proposed key table entry format. However, I'm willing to listen to
your proposal on how to handle this.

Thanks,
Acee

On 9/17/13 8:02 AM, "Sam Hartman" <hartmans-ietf@mit.edu> wrote:

>>>>>> "Joel" == Joel M Halpern <jmh@joelhalpern.com> writes:
>
>
>    Joel> The one concern I have about using a single entry and a
>    Joel> registry describing both sides is whether there will be many
>    Joel> different combinations that folks have a reason (good, bad, or
>    Joel> otherwise) to use. As long as the number of combinations is
>    Joel> small, this compound entry seems tractable.
>
>
>Agreed.
>
>I tend to give configuration and operation complexity very heavy weight
>because I want our solutions to be easy enough to deploy that they are
>actually deployed.
>So, I strongly prefer the single entry approach if the number of
>combinations is small.
>_______________________________________________
>karp mailing list
>karp@ietf.org
>https://www.ietf.org/mailman/listinfo/karp

v2.23.0 | Report a Bug | By Email