[lisp] Fwd: New Version Notification for draft-padma-ideas-problem-statement-01.txt

Padma Pillay-Esnault <padma.ietf@gmail.com> Wed, 15 March 2017 04:10 UTC

Return-Path: <padma.ietf@gmail.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E09912706D; Tue, 14 Mar 2017 21:10:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 RcnTScTFhLkN; Tue, 14 Mar 2017 21:09:59 -0700 (PDT)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (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 9343212704B; Tue, 14 Mar 2017 21:09:59 -0700 (PDT)
Received: by mail-wm0-x236.google.com with SMTP id v203so16743387wmg.0; Tue, 14 Mar 2017 21:09:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=AxOM+LqhPnhkZTnRag/8GfVJr0H++hxxJuRUAOdpKCI=; b=tkfNHTCtmqsFCDW1p7OwO69MEXf6XZvoDIMO2m8GUgt+RPJ12IPlAr+Ww2paxmReYu Wo8C5U+DoAx8Tg+yvvsXJS0ncUoCKD9AlkcrD2wGv8TGKMHlafwSWcp1jeAoVsrBio7Q FnxVejAN+2xLAOBORD8aLdDvGOWO+U32/7oVqOCOiWGK1aggxuk613DGDtMSniiwTKVA BrURAFJ/q6M5KWiF1m24kD8m319dJbVgTl8ztB45ReboiXex0NinAM/UPdvyHeqtheiF c8t0xusBQEtGl5CXs85MLevDAJVUTMBsrqai3o5+aX5zT3ikDdmqbckr01IiWe5fuZLo BxDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=AxOM+LqhPnhkZTnRag/8GfVJr0H++hxxJuRUAOdpKCI=; b=c+5zGJtEx9KLdba6nrvvMU3ykGalk+LqSP5+7vOUi1x9+maSarexMPFFrjrEFuU7XP O5mLAKV5JBLLBjPfWREEVMOExuBdRfPsDRVp/1BY0y0gkO/Ws/CVIvrW5P9LeaBD4wzH rdKgKW2r4GOXo2ErQTxI0C2bi3WMFvq3asllHSxuqAQwq9ZgXl3J0tvbRU/C2/+AzpQu 9fRQ9qa3/nSUvvbhhn9XE/Zfh2r3kn2G4x8iRnY0nMX9SdH9ncK3iCbdUuk/i45K6/4/ R7gypsifrKBNHJTWR+rW5+C7srFtC9MeCiZP8zpx61LLIJz0zFMIgjCyTCvQTBJOtLhc 9b/Q==
X-Gm-Message-State: AFeK/H2iUvmCAq5c11ZRrAVxPaDMLJTmpvYc+FBuji4R1pOTPNJFvAw8XLz2uVnM8DzcZcp60FWar5vwXw16ag==
X-Received: by 10.28.180.195 with SMTP id d186mr818740wmf.112.1489550998156; Tue, 14 Mar 2017 21:09:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.138.231 with HTTP; Tue, 14 Mar 2017 21:09:57 -0700 (PDT)
From: Padma Pillay-Esnault <padma.ietf@gmail.com>
Date: Tue, 14 Mar 2017 21:09:57 -0700
Message-ID: <CAG-CQxp4geZVcpOWVjpC4FThg3rocSm2qCFkY3Yh8DzLsYamsQ@mail.gmail.com>
To: ideas@ietf.org, LISP mailing list list <lisp@ietf.org>, NVO3 <nvo3@ietf.org>
Content-Type: multipart/alternative; boundary="001a114b61d61ebc84054abd1e91"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/NEtYhP3PxgkDNKdjMuqv6kScpEQ>
Subject: [lisp] Fwd: New Version Notification for draft-padma-ideas-problem-statement-01.txt
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 15 Mar 2017 04:10:01 -0000

Hello Everyone


We updated the IDEAS problem statement draft.

The document went under significant changes per feedback after the meeting
in IETF97.

Highlights:
- streamlined to only Problem Statement.
- added brief overview on ID based networks
- clarified the key problems
- there are two companion drafts covering the use cases and the
requirements (to be posted by tomorrow)

Comments and suggestions for improvement are welcome.

Thanks
Padma (on behalf of all contributors)


A new version of I-D, draft-padma-ideas-problem-statement-01.txt
has been successfully submitted by Padma Pillay-Esnault and posted to the
IETF repository.

Name:           draft-padma-ideas-problem-statement
Revision:       01
Title:          Problem Statement for Identity Enabled Networks
Document date:  2017-03-12
Group:          Individual Submission
Pages:          15
URL:            https://www.ietf.org/internet-drafts/draft-padma-ideas-probl
em-statement-01.txt
Status:         https://datatracker.ietf.org/doc/draft-padma-ideas-problem-
statement/
Htmlized:       https://tools.ietf.org/html/draft-padma-ideas-problem-state
ment-01
Diff:           https://www.ietf.org/rfcdiff?url2=draft-padma-ideas-problem
-statement-01

Abstract:
   The forthcoming deployment of 5G coupled with emerging applications
   such as augmented reality, virtual reality and 8k videos are likely
   to raise more stringent requirements in terms of ultra-low latency
   while ensuring session continuity.  The emergence of IoT services
   also raises new challenges (with respect to their interoperability,
   discovery, naming and addressing) which may lead to identity-based
   designs.  This problem statement examines how the existing solutions
   for networks whose forwarding scheme assumes the decoupling between
   the identifier and the locator information (called Identity Enabled
   Networks) will struggle to meet such requirements.  It advocates for
   a standardized, secured common control plane with data integrity for
   Identity Services such as identifier registration, mapping and
   resolution.  This memo also identifies several key areas to be
   further investigated for the architecture design of these services.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat