Re: [spring] draft-ginsberg-spring-conflict-resolution - IPR Call
Hello Bruno, I am also not aware of any IPR related to this draft. Thanks, Martin On 13/04/16 09:57, bruno.decra...@orange.com wrote: > Working Group, > > The authors of draft-ginsberg-spring-conflict-resolution believe that the > document is ready to be considered for working adoption. > > This mail starts the IPR poll. > > Are you aware of any IPR that applies to > draft-ginsberg-spring-conflict-resolution? > > If so, has this IPR been disclosed in compliance with IETF IPR rules (see > RFCs 3979, 4879, 3669 and 5378 for more details)? > > If you are listed as a document author or contributor please respond to this > email regardless of whether or not you are aware of any relevant IPR. The > response needs to be sent to the SPRING wg mailing list. The document will > not advance to the next stage until a response has been received from each > author and contributor. > > If you are on the SPRING WG email list but are not listed as an author or > contributor, then please explicitly respond only if you are aware of any IPR > that has not yet been disclosed in conformance with IETF rules. > > Thanks, > -- Bruno, John > > > _ > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete > this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. > > MartinPilka Mlynské Nivy 56 / 821 05 Bratislava / Slovakia +421 908 767 009 / martin.pi...@pantheon.tech reception: +421 2 206 65 111 / www.pantheon.sk [logo] ___ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
[spring] Document Action: 'SPRING Problem Statement and Requirements' to Informational RFC (draft-ietf-spring-problem-statement-08.txt)
The IESG has approved the following document: - 'SPRING Problem Statement and Requirements' (draft-ietf-spring-problem-statement-08.txt) as Informational RFC This document is the product of the Source Packet Routing in Networking Working Group. The IESG contact persons are Alvaro Retana, Alia Atlas and Deborah Brungard. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-spring-problem-statement/ Technical Summary This document lists requirements and main use-cases to be considered in the design of architectures aimed at reaching the goals of the SPRING working group. It highlights the importance of supporting both MPLS and IPv6 data-planes. Working Group Summary This document is actually a solution to a controversy at the early days of SPRING, where problem description and solutions were tied in single documents. Once the separation occurred there were no items where the consensus was rough. Document Quality A large number of vendors and operator have supported the adoption of this draft, and are also participating in the development of solutions. Personnel Pierre Francois is the Document Shepherd. Alvaro Retana is the Responsible Area Director. ___ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
Re: [spring] New Version Notification for draft-ietf-spring-segment-routing-msdc-01.txt
just a refresh with updated references. Any comments/feedbakc is welcome. Thanks. s. > On Apr 13, 2016, at 4:50 PM, internet-dra...@ietf.org wrote: > > > A new version of I-D, draft-ietf-spring-segment-routing-msdc-01.txt > has been successfully submitted by Stefano Previdi and posted to the > IETF repository. > > Name: draft-ietf-spring-segment-routing-msdc > Revision: 01 > Title:BGP-Prefix Segment in large-scale data centers > Document date:2016-04-13 > Group:spring > Pages:23 > URL: > https://www.ietf.org/internet-drafts/draft-ietf-spring-segment-routing-msdc-01.txt > Status: > https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing-msdc/ > Htmlized: > https://tools.ietf.org/html/draft-ietf-spring-segment-routing-msdc-01 > Diff: > https://www.ietf.org/rfcdiff?url2=draft-ietf-spring-segment-routing-msdc-01 > > Abstract: > This document describes the motivation and benefits for applying > segment routing in the data-center. It describes the design to > deploy segment routing in the data-center, for both the MPLS and IPv6 > dataplanes. > > > > > > 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 > ___ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
Re: [spring] draft-ginsberg-spring-conflict-resolution - IPR Call
Hi Bruno, I am not aware of any IPR that applies to this draft. thanks, Peter On 4/13/16 09:56 , bruno.decra...@orange.com wrote: Working Group, The authors of draft-ginsberg-spring-conflict-resolution believe that the document is ready to be considered for working adoption. This mail starts the IPR poll. Are you aware of any IPR that applies to draft-ginsberg-spring-conflict-resolution? If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details)? If you are listed as a document author or contributor please respond to this email regardless of whether or not you are aware of any relevant IPR. The response needs to be sent to the SPRING wg mailing list. The document will not advance to the next stage until a response has been received from each author and contributor. If you are on the SPRING WG email list but are not listed as an author or contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules. Thanks, -- Bruno, John _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. . ___ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
