Re: [lisp] LISP SDN

Robert Raszuk <robert@raszuk.net> Mon, 17 February 2014 19:14 UTC

Return-Path: <rraszuk@gmail.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6F381A03DB for <lisp@ietfa.amsl.com>; Mon, 17 Feb 2014 11:14:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jgXzKQc0xm2S for <lisp@ietfa.amsl.com>; Mon, 17 Feb 2014 11:14:49 -0800 (PST)
Received: from mail-la0-x22e.google.com (mail-la0-x22e.google.com [IPv6:2a00:1450:4010:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id F39BB1A0275 for <lisp@ietf.org>; Mon, 17 Feb 2014 11:14:48 -0800 (PST)
Received: by mail-la0-f46.google.com with SMTP id b8so11439979lan.19 for <lisp@ietf.org>; Mon, 17 Feb 2014 11:14:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=YrGF7/PeQGTXrQXZb1JjQLwuWdfwHt3k/9H8EdBesY4=; b=kECZeNdH7PYBjehFdA5RkA1zy0+9Nw8pIXNvk2p904JSDVQqrwWuyF1N0fEhpFfiC1 4p51LVh8gn0A9XLLwW3tezxZBvrA9k5Y8Fw7kcVK00NWEUytIrwSGhkSGwtxN4cUwJCZ s3UGkZ1Z1vZ/6rZcpH5szrVtErYoNInoLX7kGCWRrXsTJqaclxtK5yMOKKA2Fgp5fgDe v7t7gmwox/nyRpRw/uwBr0RKBpZr65/bFTQSyc/O2Jpnkvjt+lRkkj5zTBq1pCbkwRL5 ysrNGSbqfqDgjamvNZnSwWg8eaREEGmAUW4nEhgdypB6itJgB3ImVTFKrggnZ7XFF7u0 yH9Q==
MIME-Version: 1.0
X-Received: by 10.112.204.104 with SMTP id kx8mr17760757lbc.12.1392664485656; Mon, 17 Feb 2014 11:14:45 -0800 (PST)
Sender: rraszuk@gmail.com
Received: by 10.112.51.105 with HTTP; Mon, 17 Feb 2014 11:14:45 -0800 (PST)
In-Reply-To: <CA+YHcKF5aUK-ADsxaE7W1T9DmkON51LogDdDXVEWTq1jF5tDDA@mail.gmail.com>
References: <CA+YHcKF5aUK-ADsxaE7W1T9DmkON51LogDdDXVEWTq1jF5tDDA@mail.gmail.com>
Date: Mon, 17 Feb 2014 20:14:45 +0100
X-Google-Sender-Auth: Su1CdS8tevhClO0pXvT7U_cCOM4
Message-ID: <CA+b+ERmJsdSw+kb+oSi-yyydQrB6_uTJBXPnNT9LH9nqovLRMQ@mail.gmail.com>
From: Robert Raszuk <robert@raszuk.net>
To: Alberto Rodriguez-Natal <arnatal@ac.upc.edu>
Content-Type: multipart/alternative; boundary="001a11c3c7f0f57dc604f29ef7b5"
Archived-At: http://mailarchive.ietf.org/arch/msg/lisp/v7gZtVwhGXXb0aoL4VRLyY4CN84
Cc: "lisp@ietf.org list" <lisp@ietf.org>
Subject: Re: [lisp] LISP SDN
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 19:14:52 -0000

Hi Alberto at all,

I have read your draft with high interest expecting to understand what the
"sdn" is. And you did not let me down as the draft provided clear
definition of 5-tuples to be all the SDN magic is about:

      5-tuple: The term 5-tuple is used in this document to describe the

      set comprised by 5 elements, being these the source IP address,
      the destination IP address, the level 4 protocol number, the level
      4 protocol source port and the level 4 protocol destination port
      of a data packet.


Considering you implicitely meant IPv4 & IPv6 you have really defined
7 tuples ... 


But I must ask why limit yourself to 5 or 7 tuples if another
standards body (at least one claims to be the SDO)

already
long time
ago defined 39 tuples to be SDN primitives or building blocks.
Is there something among those

39 tuples xTRs can't do ? I guess not as both could be same boxes
from same ODM vendor :)



List of those 39ers (src: OF 1.3
http://goo.gl/a2OnWn
)
:


/* OXM Flow match field types for OpenFlow basic class. */

enum oxm_ofb_match_fields {
OFPXMT_OFB_IN_PORT = 0, /* Switch input port. */
OFPXMT_OFB_IN_PHY_PORT = 1, /* Switch physical input port. */
OFPXMT_OFB_METADATA = 2, /* Metadata passed between tables. */
OFPXMT_OFB_ETH_DST = 3, /* Ethernet destination address. */
OFPXMT_OFB_ETH_SRC = 4, /* Ethernet source address. */
OFPXMT_OFB_ETH_TYPE = 5, /* Ethernet frame type. */
OFPXMT_OFB_VLAN_VID = 6, /* VLAN id. */
OFPXMT_OFB_VLAN_PCP = 7, /* VLAN priority. */
OFPXMT_OFB_IP_DSCP = 8, /* IP DSCP (6 bits in ToS field). */
OFPXMT_OFB_IP_ECN = 9, /* IP ECN (2 bits in ToS field). */
OFPXMT_OFB_IP_PROTO = 10, /* IP protocol. */
OFPXMT_OFB_IPV4_SRC = 11, /* IPv4 source address. */
OFPXMT_OFB_IPV4_DST = 12, /* IPv4 destination address. */
OFPXMT_OFB_TCP_SRC = 13, /* TCP source port. */
OFPXMT_OFB_TCP_DST = 14, /* TCP destination port. */
OFPXMT_OFB_UDP_SRC = 15, /* UDP source port. */
OFPXMT_OFB_UDP_DST = 16, /* UDP destination port. */
OFPXMT_OFB_SCTP_SRC = 17, /* SCTP source port. */
OFPXMT_OFB_SCTP_DST = 18, /* SCTP destination port. */
OFPXMT_OFB_ICMPV4_TYPE = 19, /* ICMP type. */
OFPXMT_OFB_ICMPV4_CODE = 20, /* ICMP code. */
OFPXMT_OFB_ARP_OP = 21, /* ARP opcode. */
OFPXMT_OFB_ARP_SPA = 22, /* ARP source IPv4 address. */
OFPXMT_OFB_ARP_TPA = 23, /* ARP target IPv4 address. */
OFPXMT_OFB_ARP_SHA = 24, /* ARP source hardware address. */
OFPXMT_OFB_ARP_THA = 25, /* ARP target hardware address. */
OFPXMT_OFB_IPV6_SRC = 26, /* IPv6 source address. */
OFPXMT_OFB_IPV6_DST = 27, /* IPv6 destination address. */
OFPXMT_OFB_IPV6_FLABEL = 28, /* IPv6 Flow Label */
OFPXMT_OFB_ICMPV6_TYPE = 29, /* ICMPv6 type. */
OFPXMT_OFB_ICMPV6_CODE = 30, /* ICMPv6 code. */
OFPXMT_OFB_IPV6_ND_TARGET = 31, /* Target address for ND. */
OFPXMT_OFB_IPV6_ND_SLL = 32, /* Source link-layer for ND. */
OFPXMT_OFB_IPV6_ND_TLL = 33, /* Target link-layer for ND. */
OFPXMT_OFB_MPLS_LABEL = 34, /* MPLS label. */
OFPXMT_OFB_MPLS_TC = 35, /* MPLS TC. */
OFPXMT_OFP_MPLS_BOS = 36, /* MPLS BoS bit. */
OFPXMT_OFB_PBB_ISID = 37, /* PBB I-SID. */
OFPXMT_OFB_TUNNEL_ID = 38, /* Logical Port Metadata. */
OFPXMT_OFB_IPV6_EXTHDR = 39, /* IPv6 Extension Header pseudo-field */
};


Cheers,
R.




On Mon, Feb 17, 2014 at 5:45 PM, Alberto Rodriguez-Natal <arnatal@ac.upc.edu
> wrote:

> Dear all,
>
> We have submitted a new draft, "SDN extensions for LISP", that you can
> find here:
>
> http://tools.ietf.org/html/draft-rodrigueznatal-lisp-sdn-00
>
> We believe that LISP can serve as a southbound protocol for SDN. With this
> draft we aim to improve vanilla LISP with some extensions to make it even
> more suitable for SDN scenarios.
>
> This draft also complements and provides the foundations for the current
> LISP NFV draft.
>
> http://tools.ietf.org/html/draft-barkai-lisp-nfv-04
>
> Your thoughts and feedback on both drafts are more than welcome.
>
> Best,
> Alberto
>
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp
>
>