IETF Logo Mail Archive

Re: [lisp] LISP Use Cases

Damien Saucez <damien.saucez@gmail.com> Sat, 15 August 2015 20:32 UTC

Return-Path: <damien.saucez@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 B95031A916F for <lisp@ietfa.amsl.com>; Sat, 15 Aug 2015 13:32:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.659
X-Spam-Level:
X-Spam-Status: No, score=-0.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_24_48=1.34, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 XkawDMCap8NB for <lisp@ietfa.amsl.com>; Sat, 15 Aug 2015 13:32:21 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36D501A9147 for <lisp@ietf.org>; Sat, 15 Aug 2015 13:32:21 -0700 (PDT)
Received: by wicne3 with SMTP id ne3so43290636wic.0 for <lisp@ietf.org>; Sat, 15 Aug 2015 13:32:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:content-transfer-encoding:subject:references:from :mime-version:in-reply-to:message-id:date:cc:to; bh=LdFmIwyE/9p7LebM8IH8aOxwSbX2wUYWQCYSDtjBBkM=; b=fnJ+sPHV7jr0IVXpkZc6z9yLUxISDdXf3LckstMA7J9PosGXSKkMkXj/sKqG3xeoQ+ 5yYKpRgO5mymyYuF4aDof8vRTuwYTasAOtqfABS+wfQnsdfrwRFjwyRjOBbT/7JDLPGY KVQgsZ4q1R0o3XLrit5NhNr59RoxtmRrwWORyPHyOEKrJqNsFRGbI0GZV6AgjSIdwVIV 5tx7RWqfe7nrR+3E3azakhSZ3yo0rJS1J2dkTAURDdqViLx9WiT0ZfVxl1QJ7STX+qGm h4U1+kLVM6E024gzK9UAByIxpaN+8kaYJwEMK0U4h0gimtfFgb7N8v04SDozyohIQgc2 TbBg==
X-Received: by 10.194.95.41 with SMTP id dh9mr12886082wjb.55.1439670739970; Sat, 15 Aug 2015 13:32:19 -0700 (PDT)
Received: from [192.168.43.154] ([90.174.2.22]) by smtp.gmail.com with ESMTPSA id ll1sm9195758wic.14.2015.08.15.13.32.14 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 15 Aug 2015 13:32:15 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-E1A0FCB4-C879-44A7-9D83-B188CD846D3A"
Content-Transfer-Encoding: 7bit
References: <77630894-48BB-483D-BE68-A15555F55CE2@gigix.net> <B1A519EE-2953-4BD2-920C-45AA21617147@gmail.com> <55C92A78.2050406@joelhalpern.com> <20E63E0C-01BC-4370-9C0D-12E11630E9AA@gmail.com> <CAHANBtK5WKh-9Ljw98JwtsAc3qtgzkMu1wuZE4a3nKmOerLJTA@mail.gmail.com> <7D1E5F8A-7A83-4158-A770-4468986EC380@gmail.com> <CAHANBtLNmXuub6Y7P1v497rGWN9TvMak7y9S_beYW6xHwkg5-Q@mail.gmail.com>
From: Damien Saucez <damien.saucez@gmail.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <CAHANBtLNmXuub6Y7P1v497rGWN9TvMak7y9S_beYW6xHwkg5-Q@mail.gmail.com>
Message-Id: <C92EE070-B694-44AE-B273-4E6BBBA70C05@gmail.com>
Date: Fri, 14 Aug 2015 18:18:18 +0200
To: Stig Venaas <stig@venaas.com>
X-Mailer: iPod touch Mail (12H321)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/XIeFNeOAd30JXt_7I9Bmbf0k2rw>
Cc: LISP mailing list list <lisp@ietf.org>
Subject: Re: [lisp] LISP Use Cases
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: <https://mailarchive.ietf.org/arch/browse/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: Sat, 15 Aug 2015 20:32:22 -0000

Hello,

I understand that multicast and nat traversal are potentially required in all use cases, but the "must support" sounds extreme to me. Are they hypothetical requirements or real demand from the market targeted by LISP, new version ?

Damien Saucez 

> On 12 Aug 2015, at 19:44, Stig Venaas <stig@venaas.com> wrote:
> 
> 
> On Aug 12, 2015 10:22 AM, "Dino Farinacci" <farinacci@gmail.com> wrote:
> >
> > Yes, where but multicast sources as well as multicast receivers are moving. There are severl military applications for this use-case.
> 
> Agree
> 
> Stig
> 
> >
> > Dino
> >
> > > On Aug 12, 2015, at 10:20 AM, Stig Venaas <stig@venaas.com> wrote:
> > >
> > > I agree we need to consider multicast. There are people that want to do multicast over LISP. Some are already doing it. This also includes mobility.
> > >
> > > Stig
> >
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp

v2.23.0 | Report a Bug | By Email