[Sdn] SDN Reading List
Vipul Gautam <forvipulgautam@gmail.com> Thu, 28 July 2016 18:37 UTC
Return-Path: <forvipulgautam@gmail.com>
X-Original-To: sdn@ietfa.amsl.com
Delivered-To: sdn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD6E512DC1E for <sdn@ietfa.amsl.com>; Thu, 28 Jul 2016 11:37:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.689
X-Spam-Level:
X-Spam-Status: No, score=-2.689 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, T_MIME_MALF=0.01] 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 s4PHIiyQ_6br for <sdn@ietfa.amsl.com>; Thu, 28 Jul 2016 11:37:51 -0700 (PDT)
Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (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 58C5712DC15 for <sdn@irtf.org>; Thu, 28 Jul 2016 11:37:51 -0700 (PDT)
Received: by mail-it0-x22b.google.com with SMTP id f6so87050148ith.0 for <sdn@irtf.org>; Thu, 28 Jul 2016 11:37:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=Y2X6ur/ztaX/s6Ajaoc5O5J1u2GvOthXRzrGdkPkZic=; b=CV0VsGuRs2zu1qIHIdHiPgIcdVdKzQs13q9yKmCPBXGLhGz8d2aSfl7HMwR/vuBR8D /B1FbLd8CIpVIj4N+AXAGJZCJAanG2w2djbDghneVEh9sQRhuW/jNZCIocPWcZamKyGG JB5e7aODiNtMhf5aqWe+DmVTiDwqYyoQsVpuPHIPqaAn0M8KaT2RBJYp3sFIwTRxvYiX Q5UB8jqSgTu0SzIE1wsUborYcUvQ4PFl3z39T2rqbijNLR4YMFdSudm8CwtA2xP/E1fu Z1gR0F6Kr/JQHLiQUBcY7XCgS0jcr0TTijlbeF3Gc7mRK/EkM3WU/Q3LczZGODom8wBp aqCQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=Y2X6ur/ztaX/s6Ajaoc5O5J1u2GvOthXRzrGdkPkZic=; b=PulXnE9CqvCyx6BL8f7iN6WbgDma8ubUjUoi3SN86KxvcLOxOgiZHxr9PrfME8W5sq no7rNiQAlanlD2ehjWmqoSUChLRuJuRCG5A6vqHGp1+x5UCBVAIZvqGnMK6J49b19RBa sA0V+VAXdARUktDYz7AEKDSs4jTM6rGQ6f4IWuodvqLc741U3QDeOPPWxEqaPThJvj3c 3T6b7N5jszN7Al8ktDHH1AmIJ67qweEIejXPq4KzDmNrltmq4kMyUIbxV/LKoO86rvh6 zo6DIpb9pqfoLSAAGVSsA/EYbDsLnQZ7Pb5+mkx/nPvZ6Zp0eTJu5rQCVodmSQ4mvaAv 0BbQ==
X-Gm-Message-State: ALyK8tLcYir2p1ev+n/h+AtEnnVQbCmEBzqnPyGDQZxXdCWJalIDGSs7oBjyBr9gDLfRfkWqkPJLYGqVKsKdAA==
MIME-Version: 1.0
X-Received: by 10.36.212.132 with SMTP id x126mr94615853itg.34.1469731070407; Thu, 28 Jul 2016 11:37:50 -0700 (PDT)
Received: by 10.107.16.227 with HTTP; Thu, 28 Jul 2016 11:37:49 -0700 (PDT)
Received: by 10.107.16.227 with HTTP; Thu, 28 Jul 2016 11:37:49 -0700 (PDT)
In-Reply-To: <CAOwVEtBpT1MWXaCrR=K_a-FCBm6eNdzW=4xicLzhZK=a9DzxSg@mail.gmail.com>
References: <CAOwVEtBpT1MWXaCrR=K_a-FCBm6eNdzW=4xicLzhZK=a9DzxSg@mail.gmail.com>
Date: Fri, 29 Jul 2016 00:22:49 +0545
Message-ID: <CAOwVEtAFwnuOLMpJ7z74OudjJVfu==cSQY1h56t6veU1+-Q5xQ@mail.gmail.com>
From: Vipul Gautam <forvipulgautam@gmail.com>
To: sdn@irtf.org
Content-Type: multipart/alternative; boundary="94eb2c0b147a5df91a0538b66e4c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sdn/h6jI-mO58QAMtn7VW_bbNfIuXrg>
Subject: [Sdn] SDN Reading List
X-BeenThere: sdn@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: List to Discuss SDN Research Group in the IRTF <sdn.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/sdn>, <mailto:sdn-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sdn/>
List-Post: <mailto:sdn@irtf.org>
List-Help: <mailto:sdn-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/sdn>, <mailto:sdn-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2016 18:37:54 -0000
Dear Cristian, It's Good. I am ready to support. Best Regards, Vipul Gautam (977-9841350299) On Jul 28, 2016 00:45, <sdn-request@irtf.org> wrote: Send sdn mailing list submissions to sdn@irtf.org To subscribe or unsubscribe via the World Wide Web, visit https://www.irtf.org/mailman/listinfo/sdn or, via email, send a message with subject or body 'help' to sdn-request@irtf.org You can reach the person managing the list at sdn-owner@irtf.org When replying, please edit your Subject line so it is more specific than "Re: Contents of sdn digest..." Today's Topics: 1. SDN reading list (Cristian Lumezanu) 2. Re: [openflow-discuss] SDN reading list (HENRYDOSS, JAMES) ---------------------------------------------------------------------- Message: 1 Date: Wed, 27 Jul 2016 15:36:41 +0000 From: Cristian Lumezanu <lume@nec-labs.com> To: "sdn@irtf.org" <sdn@irtf.org>, "openflow-discuss@lists.stanford.edu" <openflow-discuss@lists.stanford.edu> Subject: [Sdn] SDN reading list Message-ID: <71448255-655A-4E36-9A61-A2F973CE5A37@nec-labs.com> Content-Type: text/plain; charset="utf-8" Hi everybody, I have been maintaining an SDN reading list ( https://sites.google.com/site/sdnreadinglist/) for the last four years. My original goal was to provide a centralized repository of SDN research to better help both newcomers and experienced researchers navigate this rather new research area. The number of hits that the website receives every day makes me think that this effort was not in vain. However, as the field of SDN has grown rapidly in the past few years, so has the number of projects, conferences, and papers that I must keep track of and update. This is slowly taking up more time than I can allocate to it and the freshness of the list suffers. Therefore, I would like to turn the SDN reading list into a collaborative project. For this, I am looking for volunteers who would like to take over the task of updating (and keeping up-to-date) small parts of the site. A ?part? could be a sub-area of SDN research, such as ?verification? or ?monitoring and measurement". If it?s your own research area, even better, you are probably following all related work anyway and would need little time to keep your part up-to-date. If you can help with this, please send me a personal email with what sub-areas you are comfortable updating and any other constraints that you may have. Even if you don?t have time for this but you have suggestions for how this reading list might better serve the community, please send them along. Cristian ------------------------------ Message: 2 Date: Wed, 27 Jul 2016 15:48:19 +0000 From: "HENRYDOSS, JAMES" <JD5401@att.com> To: Cristian Lumezanu <lume@nec-labs.com>, "sdn@irtf.org" <sdn@irtf.org>, "openflow-discuss@lists.stanford.edu" <openflow-discuss@mailman.stanford.edu> Subject: Re: [Sdn] [openflow-discuss] SDN reading list Message-ID: < CF50ADA9BA4A474C8983D1E915E2FBE9086D6946@GAALPA1MSGUSRAH.ITServices.sbc.com> Content-Type: text/plain; charset="utf-8" Hi Cristian, Please include my name. I am available to support this website. This is an excellent google page with latest updates on the SDN field. James Henrydoss (404)-345-2524 -----Original Message----- From: openflow-discuss [mailto:openflow-discuss-bounces@mailman.stanford.edu] On Behalf Of Cristian Lumezanu Sent: Wednesday, July 27, 2016 11:37 AM To: sdn@irtf.org; openflow-discuss@lists.stanford.edu < openflow-discuss@mailman.stanford.edu> Subject: [openflow-discuss] SDN reading list Hi everybody, I have been maintaining an SDN reading list ( https://sites.google.com/site/sdnreadinglist/) for the last four years. My original goal was to provide a centralized repository of SDN research to better help both newcomers and experienced researchers navigate this rather new research area. The number of hits that the website receives every day makes me think that this effort was not in vain. However, as the field of SDN has grown rapidly in the past few years, so has the number of projects, conferences, and papers that I must keep track of and update. This is slowly taking up more time than I can allocate to it and the freshness of the list suffers. Therefore, I would like to turn the SDN reading list into a collaborative project. For this, I am looking for volunteers who would like to take over the task of updating (and keeping up-to-date) small parts of the site. A ?part? could be a sub-area of SDN research, such as ?verification? or ?monitoring and measurement". If it?s your own research area, even better, you are probably following all related work anyway and would need little time to keep your part up-to-date. If you can help with this, please send me a personal email with what sub-areas you are comfortable updating and any other constraints that you may have. Even if you don?t have time for this but you have suggestions for how this reading list might better serve the community, please send them along. Cristian _______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss ------------------------------ Subject: Digest Footer _______________________________________________ sdn mailing list sdn@irtf.org https://www.irtf.org/mailman/listinfo/sdn ------------------------------ End of sdn Digest, Vol 50, Issue 7 **********************************
- Re: [Sdn] SDN Reading List Peter Edge
- Re: [Sdn] SDN Reading List Liushucheng (Will)
- Re: [Sdn] SDN Reading List Rana Sircar
- [Sdn] SDN Reading List Vipul Gautam