Re: New Version Notification for draft-herbert-fast-00.txt
Jong-Hyouk Lee <[email protected]> Wed, 24 Jan 2018 12:27:47 +0900
| Newsgroups | gmane.ietf.mip6 |
|---|---|
| Message-ID | <B190C314-AC74-480A-8457-BA61D44DC0B2__20714.9558853873$1516764387$gmane$org@gmail.com> |
--===============5849732496956441276== Content-Type: multipart/alternative; boundary="Apple-Mail=_0E8F3E08-58DF-42F4-A001-24CC114E3F4C" --Apple-Mail=_0E8F3E08-58DF-42F4-A001-24CC114E3F4C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi Tom, You may look at the following similar work presented earlier. Deprecated Network Prefix Provision: = https://tools.ietf.org/html/draft-jhlee-dmm-dnpp-01 = <https://tools.ietf.org/html/draft-jhlee-dmm-dnpp-01> Cheers. -- Jong-Hyouk Lee, living somewhere between /dev/null and /dev/random Protocol Engineering Lab., Sangmyung University #email: [email protected] #webpage: https://sites.google.com/site/hurryon > 2018. 1. 24. =EC=98=A4=ED=9B=84 12:19, Tom Herbert = <[email protected]> =EC=9E=91=EC=84=B1: >=20 > Hello, >=20 > This might be of interest to DMM group. >=20 > The basic idea of FAST (Firewall and Service Tickets) is to allow > applications to signal to the network the services they want for their > flows. The granted services are expressed in "tickets" that an > application sets in packet of of a flow (destination or nexthop > options EH). Tickets are interpreted by the ingress node of the > network and services are applied (QoS, diffserv, map to network slice, > encapsulation, etc.). Tickets are reflected by peers to get services > applied in the reverse direction. They are also stateless and in fact > a goal of FAST is to reduce flow state in the network. >=20 > Tom >=20 >=20 > ---------- Forwarded message ---------- > From: <[email protected]> > Date: Thu, Jan 11, 2018 at 11:46 AM > Subject: New Version Notification for draft-herbert-fast-00.txt > To: Tom Herbert <[email protected]> >=20 >=20 >=20 > A new version of I-D, draft-herbert-fast-00.txt > has been successfully submitted by Tom Herbert and posted to the > IETF repository. >=20 > Name: draft-herbert-fast > Revision: 00 > Title: Firewall and Service Tickets > Document date: 2018-01-11 > Group: Individual Submission > Pages: 21 > URL: = https://www.ietf.org/internet-drafts/draft-herbert-fast-00.txt > Status: https://datatracker.ietf.org/doc/draft-herbert-fast/ > Htmlized: https://tools.ietf.org/html/draft-herbert-fast-00 > Htmlized: = https://datatracker.ietf.org/doc/html/draft-herbert-fast-00 >=20 >=20 > Abstract: > This document describes the Firewalls and Service Tickets protocol. = A > ticket is data that accompanies a packet and indicates a granted > right to traverse a network or a request for network service to be > applied. Applications request tickets from a local agent in the > network and attach issued tickets to packets. Firewall tickets are > issued to grant packets the right to traverse a network; service > tickets indicate the desired service to be applied to a packets. A > single ticket may provide both firewall and service ticket > information. Tickets are sent in either IPv6 Destination options or > Hop-by-Hop options. >=20 >=20 >=20 >=20 > 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. >=20 > The IETF Secretariat >=20 > _______________________________________________ > dmm mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dmm --Apple-Mail=_0E8F3E08-58DF-42F4-A001-24CC114E3F4C Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; = charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">Hi = Tom,<div class=3D""><br class=3D""></div><div class=3D"">You may look at = the following similar work presented earlier.</div><div class=3D""><br = class=3D""></div><div class=3D"">Deprecated Network Prefix = Provision: <a = href=3D"https://tools.ietf.org/html/draft-jhlee-dmm-dnpp-01" = class=3D"">https://tools.ietf.org/html/draft-jhlee-dmm-dnpp-01</a></div><d= iv class=3D""><br class=3D""></div><div class=3D"">Cheers.<br = class=3D""><div class=3D""> --<br class=3D"">Jong-Hyouk Lee, living somewhere between /dev/null = and /dev/random<br class=3D"">Protocol Engineering Lab., = Sangmyung University<br class=3D""><br class=3D"">#<a = href=3D"mailto:[email protected]" class=3D"">email: = [email protected]</a><br class=3D"">#webpage: <a = href=3D"https://sites.google.com/site/hurryon" = class=3D"">https://sites.google.com/site/hurryon</a> </div> <div><br class=3D""><blockquote type=3D"cite" class=3D""><div = class=3D"">2018. 1. 24. =EC=98=A4=ED=9B=84 12:19, Tom Herbert <<a = href=3D"mailto:[email protected]" class=3D"">[email protected]</a>> = =EC=9E=91=EC=84=B1:</div><br class=3D"Apple-interchange-newline"><div = class=3D""><div class=3D"">Hello,<br class=3D""><br class=3D"">This = might be of interest to DMM group.<br class=3D""><br class=3D"">The = basic idea of FAST (Firewall and Service Tickets) is to allow<br = class=3D"">applications to signal to the network the services they want = for their<br class=3D"">flows. The granted services are expressed in = "tickets" that an<br class=3D"">application sets in packet of of a flow = (destination or nexthop<br class=3D"">options EH). Tickets are = interpreted by the ingress node of the<br class=3D"">network and = services are applied (QoS, diffserv, map to network slice,<br = class=3D"">encapsulation, etc.). Tickets are reflected by peers to get = services<br class=3D"">applied in the reverse direction. They are also = stateless and in fact<br class=3D"">a goal of FAST is to reduce flow = state in the network.<br class=3D""><br class=3D"">Tom<br class=3D""><br = class=3D""><br class=3D"">---------- Forwarded message ----------<br = class=3D"">From: <<a href=3D"mailto:[email protected]" = class=3D"">[email protected]</a>><br class=3D"">Date: Thu, Jan = 11, 2018 at 11:46 AM<br class=3D"">Subject: New Version Notification for = draft-herbert-fast-00.txt<br class=3D"">To: Tom Herbert <<a = href=3D"mailto:[email protected]" = class=3D"">[email protected]</a>><br class=3D""><br class=3D""><br = class=3D""><br class=3D"">A new version of I-D, = draft-herbert-fast-00.txt<br class=3D"">has been successfully submitted = by Tom Herbert and posted to the<br class=3D"">IETF repository.<br = class=3D""><br class=3D"">Name: = draft-herbert-= fast<br class=3D"">Revision: 00<br = class=3D"">Title: = Firewall and = Service Tickets<br class=3D"">Document date: 2018-01-11<br = class=3D"">Group: = Individual = Submission<br class=3D"">Pages: = 21<br = class=3D"">URL: = <a = href=3D"https://www.ietf.org/internet-drafts/draft-herbert-fast-00.txt" = class=3D"">https://www.ietf.org/internet-drafts/draft-herbert-fast-00.txt<= /a><br class=3D"">Status: = <a = href=3D"https://datatracker.ietf.org/doc/draft-herbert-fast/" = class=3D"">https://datatracker.ietf.org/doc/draft-herbert-fast/</a><br = class=3D"">Htmlized: <a = href=3D"https://tools.ietf.org/html/draft-herbert-fast-00" = class=3D"">https://tools.ietf.org/html/draft-herbert-fast-00</a><br = class=3D"">Htmlized: <a = href=3D"https://datatracker.ietf.org/doc/html/draft-herbert-fast-00" = class=3D"">https://datatracker.ietf.org/doc/html/draft-herbert-fast-00</a>= <br class=3D""><br class=3D""><br class=3D"">Abstract:<br class=3D""> = This document describes the Firewalls and Service Tickets = protocol. A<br class=3D""> ticket is data that accompanies a = packet and indicates a granted<br class=3D""> right to = traverse a network or a request for network service to be<br class=3D""> = applied. Applications request tickets from a local agent in = the<br class=3D""> network and attach issued tickets to = packets. Firewall tickets are<br class=3D""> issued to grant = packets the right to traverse a network; service<br class=3D""> = tickets indicate the desired service to be applied to a = packets. A<br class=3D""> single ticket may provide both = firewall and service ticket<br class=3D""> information. = Tickets are sent in either IPv6 Destination options or<br class=3D""> = Hop-by-Hop options.<br class=3D""><br class=3D""><br = class=3D""><br class=3D""><br class=3D"">Please note that it may take a = couple of minutes from the time of submission<br class=3D"">until the = htmlized version and diff are available at <a = href=3D"http://tools.ietf.org" class=3D"">tools.ietf.org</a>.<br = class=3D""><br class=3D"">The IETF Secretariat<br class=3D""><br = class=3D"">_______________________________________________<br = class=3D"">dmm mailing list<br class=3D""><a href=3D"mailto:[email protected]" = class=3D"">[email protected]</a><br = class=3D"">https://www.ietf.org/mailman/listinfo/dmm<br = class=3D""></div></div></blockquote></div><br = class=3D""></div></body></html>= --Apple-Mail=_0E8F3E08-58DF-42F4-A001-24CC114E3F4C-- --===============5849732496956441276== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm --===============5849732496956441276==--