Re: [secdir] secdir review of draft-templin-aero-10

"Fred L. Templin" <> Thu, 26 April 2012 01:51 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AD52421E80C5 for <>; Wed, 25 Apr 2012 18:51:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -100.616
X-Spam-Status: No, score=-100.616 tagged_above=-999 required=5 tests=[AWL=-0.418, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_25=0.6, J_CHICKENPOX_27=0.6, J_CHICKENPOX_28=0.6, J_CHICKENPOX_75=0.6, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 1-E6iIGCMybZ for <>; Wed, 25 Apr 2012 18:51:58 -0700 (PDT)
Received: from ( []) by (Postfix) with SMTP id B992721E80CA for <>; Wed, 25 Apr 2012 18:51:57 -0700 (PDT)
Received: from [] by with NNFMP; 26 Apr 2012 01:51:57 -0000
Received: from [] by with NNFMP; 26 Apr 2012 01:51:57 -0000
Received: from [] by with NNFMP; 26 Apr 2012 01:51:57 -0000
X-Yahoo-Newman-Property: ymail-3
Received: (qmail 20626 invoked by uid 60001); 26 Apr 2012 01:51:57 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=s1024; t=1335405117; bh=hrFR1Lk+95T8DbfCxFYIzkwuG1o6tU5PHYpX+F+gAAk=; h=X-YMail-OSG:Received:X-RocketYMMF:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=DX4aT6PqrOuCxxD79IAOAkLBCM/Eqb/s38F0Pl5jFHLF8CbFmZ2gJa7nrM3xhiYxyqg4dlYMLfRBvnWWm5RJB/UWiFV9oWrLk6hfgo+/LWzkuT0SahMaoI2TjdTrvtcFfe844jxnBBHw7i2RipCuBLk0NkxfYKGMxkF6CQcRNVU=
X-YMail-OSG: zZ6KoZEVM1mVvYqca50Q4CNJdzunc0n9j5Q2lfW4E48X8hE W_vZZid2nwE1lpnN91x04LMpdQ2U_A7NHKWJVL6GUi8twTwe_2VW0BlUjgFp WFAl7z8OvNJiJP_4WutB1QUiUmFWGxcscfWIHFSJ1TnCn1MOE23h0nTnsh.s 4YHtXPtdIUAP7oNAqfF0VBe4dcS_kkiznvH7qQx6QRbhlFXbfQDAZ.zV9qrr TprnybkYkaEA8u8lScHfCDeugRp9yHojeMdV9oFbnX3kcsYNIzOd_s9bZb8n AJuES5B.lqZRVA3EmfJCxCyMHbnFRUk1Aa3FVCPSdBIlqNSuqMOb3YYsUBNB UQl7S.6y5WizfYtCEgAaSJdqvMVwGwzxjAWrMCNBYdzSPKUJlZWOuVsfMLT4 LaXiMihqtrTatoDEDxPO4PWBOKNCC3WP25T4eRCCtdBMTkBbIlEelnIOMQDg 4UkGCDlRYwoE9HpfLQ98YxHkPUndbW3ub9cZpA1uvJDVho1jK6Zg-
Received: from [] by via HTTP; Wed, 25 Apr 2012 18:51:56 PDT
X-RocketYMMF: fltemplin
X-Mailer: YahooMailWebService/
References: <> <> <> <> <> <>
Message-ID: <>
Date: Wed, 25 Apr 2012 18:51:56 -0700 (PDT)
From: "Fred L. Templin" <>
To: Sean Turner <>
In-Reply-To: <>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-83809723-874235264-1335405116=:20323"
X-Mailman-Approved-At: Sun, 29 Apr 2012 06:46:22 -0700
Cc: "" <>, The IESG <>, "" <>
Subject: Re: [secdir] secdir review of draft-templin-aero-10
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "Fred L. Templin" <>
List-Id: Security Area Directorate <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 26 Apr 2012 01:51:59 -0000

Hi Sean,

Thanks for your point about occasional attempts to deprecate IPsec AH. What
I have in mind for AERO is something sort of like IPsec AH but much lighter
weight. I have the design worked out in my head and could use some input
from others, but is this the correct forum to kick ideas around?


> From: Sean Turner <>
>To: Fred Templin <> 
>Cc: Joe Salowey <>om>; "" <>rg>; The IESG <>rg>; "" <> 
>Sent: Wednesday, April 25, 2012 12:12 PM
>Subject: Re: [secdir] secdir review of draft-templin-aero-10
>On 4/24/12 6:55 PM, Joe Salowey wrote:
>> On Apr 24, 2012, at 11:14 AM, Fred Templin wrote:
>>> Hello Joe,
>>> Thank you for your comments. To your question on specifying a digital
>>> signing mechanism, would the concern be addressed if I were to say
>>> something like: "e.g., using IPsec AH, etc." ?
>> [Joe] Not really.  What I'm looking for is something that specifies the mechanism and how its used.  Something like
>> "Implementations MUST support<IPSEC AH>  as a means to authenticate the origin of the AERO messages.  AERO peers MUST support establishing an<IPSEC SA>  using<IKEv2>  with<certificates>  as specified in<external reference>.   During<SA>  establishment AERO hosts MUST be able identify AERO intermediate routers through mechanism defined in<RFCxxxx or section y.yy>.  "
>> The stuff in the<>  should be replaced with something that makes sense.  I'm not sure that IPSEC AH or any of the other things in<>  are really appropriate in this case.  The idea here is that there is some minimum mechanism that implementations can use to secure these messages. Securing the messages involves the transform for authenticating the messages (perhaps IPSEC AH), mechanism for key management perhaps (IKV2 with certificates) and a way to establish that you are taking to the right router (perhaps be able to match a field in a certificate to a particular name or domain).   My hope is that there already is something that would fit the bill and we could just reference that specification.  Some of the SEND variants may be useful in this scenario,  but I didn't get a chance to dig into this.
>Note that every so often somebody tries to deprecate AH because very few 
>folks use it.
>> Joe
>>> Fred
>>> ----- Original Message -----
>>>> From: Joe Salowey<>
>>>> To: Fred Templin<>
>>>> Cc: ""<>; The IESG<>rg>; ""<>
>>>> Sent: Tuesday, April 24, 2012 10:47 AM
>>>> Subject: Re: secdir review of draft-templin-aero-10
>>>> T hanks for the quick response, comments inline:
>>>> On Apr 23, 2012, at 9:52 AM, Fred Templin wrote:
>>>>> (Resending with comments as inline text)
>>>>> Hello Joe,
>>>>> Thank you for these comments. Please see below for my proposed
>>>>> resolutions:
>>>>> Fred
>>>>> From: Joe Salowey<>
>>>>> To:; The IESG<>rg>;
>>>>> Sent: Sunday, April 22, 2012 3:00 PM
>>>>> Subject: secdir review of draft-templin-aero-10
>>>>> I have reviewed this document as part of the security directorate's
>>>>> ongoing effort to review all IETF documents being processed by the
>>>>> IESG.  These comments were written primarily for the benefit of the
>>>>> security area directors.  Document editors and WG chairs should treat
>>>>> these comments just like any other last call comments.
>>>>> I apologize for the delay in getting this review out.  Hopefully it is
>>>> still useful.
>>>>> This first set of comments is primarily for the authors.
>>>>> 1. In section 4.4.4 on Data origin authentication the last paragraph states
>>>> that only the 3rd of the above conditions is acceptable, do you really mean the
>>>> 4th?
>>>>>>>> Begin FLT response
>>>>> You are correct; this should say the 4th and can be fixed in the next
>>>> version.
>>>>>>>> End FLT response
>>>> [Joe] OK
>>>>> 2. In section 4.4.4 there is reference to the packet including a digital
>>>> signature to authenticate the origin.  What is the signature mechanism?  Is this
>>>> SEND or something different? I did not see a reference to it.
>>>>>>>> Begin FLT response
>>>>> The digital signature mechanism is out of scope for this document. The text
>>>>> could be adjusted to say: “…, AERO nodes may be obliged to require the
>>>>> use of digital signatures applied through means outside the scope of this
>>>>> document.”
>>>>>>>> End FLT response
>>>> [Joe] I was hoping that something would be specified for interoperability,  I
>>>> think there are many cases where you would have to resort to a signing
>>>> mechanism, however it may be the case that AERO may be deployed where spoofing
>>>> of messages is not a concern (perhaps this should be the recommendation until a
>>>> signing mechanism is specified).  The ADs can decide if this is an issue or not.
>>>>> 3. The security considerations do not say much about the consequences of
>>>> trusting an inappropriate intermediate router, ingress node or egress node.
>>>> Clearly DOS to the ingress node is a possibility.  Data modification and
>>>> disclosure can be a goal of an attacker who tries to control the routing.  Are
>>>> there other issues the reader should be aware of (perhaps other DOS attacks such
>>>> as amplification attacks).  Anything outside the considerations of RFC4861)?
>>>>>>>> Begin FLT response
>>>>> Proposed resolution is to re-write the first paragraph of Section 6 as
>>>> follows:
>>>>> “AERO link security considerations are the same as for standard IPv6
>>>> Neighbor Discovery
>>>>> (RFC4861) except that AERO improves on some aspects. In particular, AERO is
>>>> dependent
>>>>> on a trust basis between AERO edge nodes and intermediate routers, where
>>>> the edge nodes
>>>>> must only engage in the AERO mechanism when it is facilitated by a trusted
>>>> intermediate
>>>>> router.”
>>>>>>>> End FLT response
>>>> [Joe] OK thanks.
>>>>> 4. The security consideration section indicates that spoofing protection
>>>> can be provided by links that provide link layer security mechanisms.    Link
>>>> Layer security mechanisms may or may not help.  I believe more information is
>>>> needed here.  L2 mechanisms may not provide adequate protection of upper layer
>>>> address bindings.  In some cases L2 mechanisms do not provide source origin
>>>> authentication such as multicast  traffic protected with the group  key in WiFi
>>>> and group security associations in 802.1AE (MACSEC).
>>>>>>>> Begin FLT response
>>>>> Proposed resolution is to re-write the second paragraph of Section 6 as
>>>> follows:
>>>>> “AERO links must be protected against spoofing attacks in which an attacker
>>>>> on the link pretends to be a trusted neighbor.  Links that provide
>>>> link-layer
>>>>> securing mechanisms (e.g., WiFi networks) and links that provide physical
>>>>> security (e.g., enterprise network LANs) provide only a fist-line of
>>>> defense.
>>>>> In some instances, therefore, additional securing assurances against
>>>> on-link
>>>>> spoofing attacks are required. For example, if the source can through some
>>>>> means digitally sign its messages the destination can verify the signatures
>>>> to
>>>>> ensure data origin authentication. Exact mechanisms for digitally signing
>>>> and
>>>>> verifying signatures are outside the scope of this document.”
>>>>>>>> End FLT response
>>>> [Joe] Thanks. (same comment on the specification of the signing mechanism as
>>>> above).
>>>>> This set of comments is mostly for the area directors:
>>>>> 1. I am mostly concerned about the lack of definition for the digital
>>>> signature mechanism.  Perhaps this is easily rectified by a reference to an
>>>> existing specification. Its not clear to me what the specification would be
>>>> (perhaps SEND??)?  Is something needed in addition?
>>>>> 2.  The risks of not securing the proposal are not defined in the security
>>>> considerations section. I think this would be helpful, but may not be strictly
>>>> necessary.  There is some mention of Link-Layer security helping in some aspects
>>>> of this, but its not clear on what characteristics the lower layer security
>>>> needs to provide.
>>>>> Cheers,
>>>>> Joe
>> _______________________________________________
>> secdir mailing list
>> wiki: