[karp] Comment on LMP Analysis Presentation

Acee Lindem <acee.lindem@ericsson.com> Wed, 31 July 2013 12:05 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 CE82D11E8171 for <karp@ietfa.amsl.com>; Wed, 31 Jul 2013 05:05:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 TFNI6ofw26fP for <karp@ietfa.amsl.com>; Wed, 31 Jul 2013 05:05:06 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id BA17D21F8C4B for <karp@ietf.org>; Wed, 31 Jul 2013 05:05:05 -0700 (PDT)
X-AuditID: c6180641-b7f986d000007a82-e8-51f8fd70085d
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id E0.0B.31362.07DF8F15; Wed, 31 Jul 2013 14:05:04 +0200 (CEST)
Received: from EUSAAMB101.ericsson.se ([147.117.188.118]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.02.0328.009; Wed, 31 Jul 2013 08:05:04 -0400
From: Acee Lindem <acee.lindem@ericsson.com>
To: "karp@ietf.org" <karp@ietf.org>
Thread-Topic: Comment on LMP Analysis Presentation
Thread-Index: AQHOjeYwb56tHAOB8EKSK5T30YQ5Hw==
Date: Wed, 31 Jul 2013 12:05:04 +0000
Message-ID: <94A203EA12AECE4BA92D42DBFFE0AE4702FD52D2@eusaamb101.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.5.121010
x-originating-ip: [147.117.188.134]
Content-Type: multipart/alternative; boundary="_000_94A203EA12AECE4BA92D42DBFFE0AE4702FD52D2eusaamb101erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrMLMWRmVeSWpSXmKPExsUyuXRPuG7B3x+BBrf+W1vs/baG0aKj+S2L A5PHkiU/mTw+bGpmC2CK4rJJSc3JLEst0rdL4Mpo+3uHseCreMWdjXuZGxgvC3cxcnBICJhI TPxk28XICWSKSVy4t56ti5GLQ0jgKKNEw4sNrBDOckaJi99nMoFUsQnoSDx/9I8ZpFlEQFni wNcMkDCzgKLEpO/b2UHCwgK6Ehu/soOERQSMJDbv72CEsPUk3p+bChZnEVCVmHJmGlicV8BX ondvN9h0RqAbvp9awwQxUlzi1pP5TBC3CUgs2XOeGcIWlXj5+B8riC0KNLPt2Bl2iLiyxJIn +1kgevMlflzqY4KYLyhxcuYTlgmMIrOQjJ2FpGwWkjKIuI7Egt2f2CBsbYllC18zw9hnDjyG 6rWW2Ht6AxOymgWMHKsYOUqLU8ty040MNzECI+qYBJvjDsYFnywPMUpzsCiJ827QOxMoJJCe WJKanZpakFoUX1Sak1p8iJGJg1OqgXHB5ZhJsz3/n9uvs1pou/DNiFdPUxoPJ8YF8/2t+z2r fkX7vp53zmq/VkrcmLzBMy2aI3TnqiXdHW/XnXl6+6dC0fstc7P/CJ7+4Mi8R5VFatmifR5n l4gy7ZG8wsz1zzT18KTp3P68nhHL7fb6HMku/t8iXX+ohv1BvV16XrFr4u9J9yaLrlmkxFKc kWioxVxUnAgA5nafvXYCAAA=
Subject: [karp] Comment on LMP Analysis Presentation
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: Wed, 31 Jul 2013 12:05:13 -0000

Hi Mahesh, et al,

I couldn't find the requirement for TCP packets in the LMP protocol. Perhaps, it isn't needed. I'm not an LMP expert but there could be confusion due to the reuse  of the ASON terminology. See this excerpt from RFC 4394:


2.  ASON Terminology and Abbreviations Related to Discovery

   ITU-T Recommendation G.8080 Amendment 1 [G.8080] and ITU-T
   Recommendation G.7714 [G.7714] provide definitions and mechanisms
   related to transport plane discovery.

   Note that in the context of this work, "Transport" relates to the
   data plane (sometimes called the transport plane or the user plane)
   and does not refer to the transport layer (layer 4) of the OSI seven
   layer model, nor to the concept of transport intended by protocols
   such as the Transmission Control Protocol (TCP).

   Special care must be taken with the acronym "TCP", which within the
   context of the rest of this document means "Termination Connection
   Point" and does not indicate the Transmission Control Protocol.


Thanks,

Acee