- ipv6-wg - mailman.ripe.net

Fw: (IPng 7140) New IPng Internet Draft Procedure
by Thomas Trede 31 Jan '99

31 Jan '99

-----Urspr|ngliche Nachricht----- Von: Bob Hinden <hinden(a)iprg.nokia.com> An: ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM> Cc: hinden(a)iprg.nokia.com <hinden(a)iprg.nokia.com>; deering(a)cisco.com <deering(a)cisco.com> Datum: Freitag, 29. Januar 1999 20:01 Betreff: (IPng 7140) New IPng Internet Draft Procedure >Please note that all new IPng Internet drafts submitted on or after >February 1, 1999 need to follow the procedure described in the attached email. > >This procedure includes the following: > > "All Internet-Drafts must begin with ONE of the following three > statements: > > This document is an Internet-Draft and is in full conformance > with all provisions of Section 10 of RFC2026. > > This document is an Internet-Draft and is in full conformance > with all provisions of Section 10 of RFC2026 except for the > right to produce derivative works. > > This document is an Internet-Draft and is NOT offered in > accordance with Section 10 of RFC2026, and will only exist as > an Internet-Draft. > > Any submission which does not include one (and only one) of the above > three statements will be returned to the submitter. The IETF > Secretariat will NOT add this text." > >The IPng w.g. chairs require anyone considering the submission an IPng >Internet Draft (i.e. draft-ietf-ipngwg-xxxx) that does not include the >first statement obtain permission from the chairs prior to publication. >Without the first statement is not possible to consider the draft for entry >into the standards process. > >Bob Hinden / Steve Deering >IPng w.g. Chairs > > >>To: IETF-Announce:; >>Subject: Revised Internet-Draft boilerplate >>From: The IESG <iesg-secretary(a)ietf.org> >>Date: Fri, 29 Jan 1999 11:23:40 -0500 >>Sender: scoya(a)ns.cnri.reston.va.us >> >> >>Following up on the discussion in the plenary session at the IETF meeting in >>Orlando and the discussion on the poised mailing list, the IESG on Thursday, >>January 28th approved the new boilerplate text that must be included with >>all Internet-Draft submissions. >> >>Beginning Monday, February 1, all Internet-Draft submissions must include >>the new boilerplate. Any submissions that do not use the new text will >>be returned to the author/submitter. >> >>The new template can be accessed with this URL: >> >> http://www.ietf.org/ietf/1id-guidelines.txt >> >> >> > > >-------------------------------------------------------------------- >IETF IPng Working Group Mailing List >IPng Home Page: http://playground.sun.com/ipng >FTP archive: ftp://playground.sun.com/pub/ipng >Direct all administrative requests to majordomo(a)sunroof.eng.sun.com >-------------------------------------------------------------------- >

1 0

Fw: (IPng 7125) UPDATED AGENDA - V6 Deploy 3rd Day
by Thomas Trede 28 Jan '99

28 Jan '99

FYI. Regards, Thomas Trede -----Urspr|ngliche Nachricht----- Von: Jim Bound <bound(a)wasted.zk3.dec.com> An: ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM>; ngtrans(a)sunroof.Eng.Sun.COM <ngtrans(a)sunroof.Eng.Sun.COM>; 6bone(a)isi.edu <6bone(a)isi.edu>; v6-deployment-cabal(a)alpha.zk3.dec.com <v6-deployment-cabal(a)alpha.zk3.dec.com> Datum: Donnerstag, 28. Januar 1999 17:54 Betreff: (IPng 7125) UPDATED AGENDA - V6 Deploy 3rd Day >Folks, > >OK I added the last three requests including the one Bob F got on >ngtrans just now. > >Any more changes will have to be done on the fly folks. > >A saying for IPv6'ers: > > Poor or late Planning on your part does not constitute an emergency > on the WG, Authors, IESG, or Chairs part -----).... > >/jim > >=== >Thursday, February 4 -- IPv6 Deployment and Promotion >----------------------------------------------------- >The purpose of this day will be to review current deployment >activities, potential additional efforts, and opportunities for >educating and influencing developers, ISPs, network managers, and >users. This will include answering the following questions: >- Why would anyone run IPv6 now? >- Why would anyone ever run IPv6? >- Who will deploy IPv6 first? >- Will the Internet lead Corporate networks or follow as IPv6 is >deployed? >- How to get ISPs to deploy IPv6? > >We would like to request that each attendee come with answers to the >above questions for discussion on this 3rd day. > >This is the Final Agenda before Grenbole. We will do Agenda Bashing at >Grenoble and select order and times. > >Agenda: >(1) Discussion of the questions above. >(2) Existing deployment efforts: >- 6BONE (who?) >- 6REN (who?) >(3) Potential efforts: >- IPv6 Exchanges (who?) >- Corporate Plans (who?) >- ISP Plans (who?) >- ... >(4) Promotion >- IPv6.org (who?) >- Influencing developers, vendors, etc. (who?) >(5) Presentations: >- Bob Fink - 6REN and 6TAP >- Jim Bound - The Palo Alto Gateway and IPv6 and sub-TLA Request Strategy >- Marc Blanchet - IPv6 Deployment Issues >- Henk Steenman - Amsterdam Internet Exchange (AMS-IX) native IPv6 environment >- Jim Bound for Perry Metzger - Status of the V6 Deployment List Activities >- Jun Murai - IPv6 Deployment in Japan >- Paula Caslav - Proposed Guidelines RIPE NCC Regional Registries for IPv6 >- Jun-ichiro itojun Hagino - IPv6 verification technologies and open > result by FREE see: > http://www.tahil.org/ >- Latif LADID - Influencing IPv6 Developers and Promotion >- Kenji OTA - IETF Terminal Room Experiences with IPv6 >(6) Public Domain Code Needs for IPv6 Discussion >- Appache Web Server >- Sendmail >- BIND >- BSD Network Utilities > >thanks >/jim >-------------------------------------------------------------------- >IETF IPng Working Group Mailing List >IPng Home Page: http://playground.sun.com/ipng >FTP archive: ftp://playground.sun.com/pub/ipng >Direct all administrative requests to majordomo(a)sunroof.eng.sun.com >-------------------------------------------------------------------- >

1 0

Fw: (IPng 7118) I-D ACTION:draft-ietf-ipngwg-resv-anycast-02.txt
by Thomas Trede 28 Jan '99

28 Jan '99

FYI. Regards, Thomas Trede -----Original Message----- From: Internet-Drafts(a)ietf.org <Internet-Drafts(a)ietf.org> To: "IETF-Announce:;;;;@ns.cnri.reston.va.us;"@Eng.Sun.COM;;; <"IETF-Announce:;;;;@ns.cnri.reston.va.us;"@Eng.Sun.COM;;;> Cc: ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM> Date: Donnerstag, 28. Januar 1999 16:47 Subject: (IPng 7118) I-D ACTION:draft-ietf-ipngwg-resv-anycast-02.txt >A New Internet-Draft is available from the on-line Internet-Drafts directories. >This draft is a work item of the IPNG Working Group of the IETF. > >Note: This revision reflects comments received during the last call period. > > Title : Reserved IPv6 Subnet Anycast Addresses > Author(s) : D. Johnson, S. Deering > Filename : draft-ietf-ipngwg-resv-anycast-02.txt > Pages : 6 > Date : 27-Jan-99 > > The IP Version 6 addressing architecture defines an 'anycast' address > as an IPv6 address that is assigned to one or more network interfaces > (typically belonging to different nodes), with the property that > a packet sent to an anycast address is routed to the 'nearest' > interface having that address, according to the routing protocols' > measure of distance. This document defines a set of reserved anycast > addresses within each subnet prefix, and lists the initial allocation > of these reserved subnet anycast addresses. > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-resv-anycast-02.txt > >Internet-Drafts are also available by anonymous FTP. Login with the username >"anonymous" and a password of your e-mail address. After logging in, >type "cd internet-drafts" and then > "get draft-ietf-ipngwg-resv-anycast-02.txt". > >A list of Internet-Drafts directories can be found in >http://www.ietf.org/shadow.html > >Internet-Drafts can also be obtained by e-mail. > >Send a message to: > mailserv(a)ietf.org. >In the body type: > "FILE /internet-drafts/draft-ietf-ipngwg-resv-anycast-02.txt". > >NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > >Below is the data which will enable a MIME compliant mail reader >implementation to automatically retrieve the ASCII version of the >Internet-Draft. > ENCODING mime FILE /internet-drafts/draft-ietf-ipngwg-resv-anycast-02.txt

1 0

Fw: (IPng 7117) I-D ACTION:draft-ietf-ipngwg-router-renum-07.txt
by Thomas Trede 28 Jan '99

28 Jan '99

FYI. Regards, Thomas Trede -----Original Message----- From: Internet-Drafts(a)ietf.org <Internet-Drafts(a)ietf.org> To: "IETF-Announce:;;;;@ns.cnri.reston.va.us;"@Eng.Sun.COM;;; <"IETF-Announce:;;;;@ns.cnri.reston.va.us;"@Eng.Sun.COM;;;> Cc: ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM> Date: Donnerstag, 28. Januar 1999 16:47 Subject: (IPng 7117) I-D ACTION:draft-ietf-ipngwg-router-renum-07.txt >A New Internet-Draft is available from the on-line Internet-Drafts directories. >This draft is a work item of the IPNG Working Group of the IETF. > >Note: This revision reflects comments received during the last call period. > > Title : Router Renumbering for IPv6 > Author(s) : M. Crawford > Filename : draft-ietf-ipngwg-router-renum-07.txt > Pages : 26 > Date : 27-Jan-99 > > IPv6 Neighbor Discovery and Address Autoconfiguration conveniently > make initial assignments of address prefixes to hosts. Aside from > the problem of connection survival across a renumbering event, these > two mechanisms also simplify the reconfiguration of hosts when the > set of valid prefixes changes. > > This document defines a mechanism called Router Renumbering ('RR') > which allows address prefixes on routers to be configured and > reconfigured almost as easily as the combination of Neighbor > Discovery and Address Autoconfiguration works for hosts. It > provides a means for a network manager to make updates to the > prefixes used by and advertised by IPv6 routers throughout a site. > >A URL for this Internet-Draft is: >http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-router-renum-07.txt > >Internet-Drafts are also available by anonymous FTP. Login with the username >"anonymous" and a password of your e-mail address. After logging in, >type "cd internet-drafts" and then > "get draft-ietf-ipngwg-router-renum-07.txt". > >A list of Internet-Drafts directories can be found in >http://www.ietf.org/shadow.html >or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > >Internet-Drafts can also be obtained by e-mail. > >Send a message to: > mailserv(a)ietf.org. >In the body type: > "FILE /internet-drafts/draft-ietf-ipngwg-router-renum-07.txt". > >NOTE: The mail server at ietf.org can return the document in > MIME-encoded form by using the "mpack" utility. To use this > feature, insert the command "ENCODING mime" before the "FILE" > command. To decode the response(s), you will need "munpack" or > a MIME-compliant mail reader. Different MIME-compliant mail readers > exhibit different behavior, especially when dealing with > "multipart" MIME messages (i.e. documents which have been split > up into multiple messages), so check your local documentation on > how to manipulate these messages. > > >Below is the data which will enable a MIME compliant mail reader >implementation to automatically retrieve the ASCII version of the >Internet-Draft. > ENCODING mime FILE /internet-drafts/draft-ietf-ipngwg-router-renum-07.txt

1 0

agenda v2 for IPv6 working group RIPE32
by David Kessens 28 Jan '99

28 Jan '99

Hi, Below follows the most recent version of the IPv6 wg's agenda. David K. --- Proposed Agenda (draft v2) for the IPv6 Working Group Meeting RIPE32, Januari 1999, Amsterdam A. Administrative stuff (David Kessens, chair, 5min) - appointment of scribe - agenda bashing B. Selection of chair C. Review of action points: 31.1 RIPE NCC will start allocating IPv6 addresses by the next RIPE meeting in January. 31.2 send out to 1) experienced people draft documents about address registration and allocation 2) concerned WGs more finalized papers to stress the discussion and have working papers ready by the end of '98. D. Status of 6bone (David Kessens) E. 6REN - first IPv6 production network (David Kessens, presentation originally from Bob Fink) F. IPv6 allocation progress (Paula Caslav) - discussion of 'IPv6 ASSIGNMENT AND ALLOCATION POLICY DOCUMENT (3rd draft)' G. Experience from ISPs with IPv6 (input from audience requested) H. Future directions of the wg Z. AOB

1 0

(IPng 7100) I-D ACTION:draft-ietf-ipngwg-bsd-api-new-06.txt (fwd)
by Thomas Trede 27 Jan '99

27 Jan '99

FYI. Regards, Thomas Trede ---------- Forwarded message ---------- Date: Wed, 27 Jan 1999 11:29:58 -0500 From: Internet-Drafts(a)ietf.org To: IETF-Announce:;;;;@ns.cnri.reston.va.us;@Eng.Sun.COM;;; Cc: ipng(a)sunroof.Eng.Sun.COM Subject: (IPng 7100) I-D ACTION:draft-ietf-ipngwg-bsd-api-new-06.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IPNG Working Group of the IETF. Title : Basic Socket Interface Extensions for IPv6 Author(s) : R. Gilligan, S. Thomson, J. Bound, W. Stevens Filename : draft-ietf-ipngwg-bsd-api-new-06.txt Pages : 33 Date : 26-Jan-99 The de facto standard application program interface (API) for TCP/IP applications is the 'sockets' interface. Although this API was developed for Unix in the early 1980s it has also been implemented on a wide variety of non-Unix systems. TCP/IP applications written using the sockets API have in the past enjoyed a high degree of portability and we would like the same portability with IPv6 applications. But changes are required to the sockets API to support IPv6 and this memo describes these changes. These include a new socket address structure to carry IPv6 addresses, new address conversion functions, and some new socket options. These extensions are designed to provide access to the basic IPv6 features required by TCP and UDP applications, including multicasting, while introducing a minimum of change into the system and providing complete compatibility for existing IPv4 applications. Additional extensions for advanced IPv6 features (raw sockets and access to the IPv6 extension headers) are defined in another document [4]. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ipngwg-bsd-api-new-06.txt Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-ipngwg-bsd-api-new-06.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv(a)ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-ipngwg-bsd-api-new-06.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft.

1 0

Fw: (ngtrans) NATPT comments on Last Call
by Thomas Trede 27 Jan '99

27 Jan '99

FYI. Regards, Thomas Trede -----Original Message----- From: George Tsirtsis <george(a)gideon.bt.co.uk> To: Bob Fink <fink(a)es.net> Cc: ngtrans <ngtrans(a)sunroof.Eng.Sun.COM> Date: Mittwoch, 27. Januar 1999 13:41 Subject: (ngtrans) NATPT comments on Last Call >Bob and ngtrans falks, > >Since Kazu made a couple of fair points (thanks Kazu!) we will update the >NAT-PT draft (v5!)for one more time. Since this is the 2nd WG Last Call >and in order to avoid another update of the draft I would request from >people who are interested in this draft to have a final look and make sure >we get **comments by the end of next week** (Friday, after the Grenoble >meeting). > >This way we will be able to produce the final version and send it to the >IESG as fast as the process allows. > >Thanks for helping to clear up this document. > >See you soon (maybe in Grenoble!) > >George > >

1 0

Fw: (IPng 7094) the task of discussion leaders for Tuesday's meeting
by Thomas Trede 27 Jan '99

27 Jan '99

FYI. Regards, Thomas Trede -----Urspr|ngliche Nachricht----- Von: Steve Deering <deering(a)cisco.com> An: ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM> Cc: Bob Hinden <hinden(a)iprg.nokia.com> Datum: Mittwoch, 27. Januar 1999 01:53 Betreff: (IPng 7094) the task of discussion leaders for Tuesday's meeting >If you are one of the lucky folks named, or planning to volunteer, as a >discussion leader for the "Identify important new IPv6 protocol/standards >work" part of Tuesday's IPng WG meeting, and are wondering what a >discussion leader is expected to do, here's an answer: > > Describe the issue/problem, and its significance. Identify known > solutions, possible solutions, or possible directions in which > solutions might be found. Express an opinion about whether or not > the solution(s) require new research, new architecture, new > protocol(s), or new operational methods. Solicit input on the above > from the meeting attendees. And be prepared to do all of that in as > little as 15 minutes (worst case), if necessary. > > The goal of the exercise is to decide on what action should be taken > to address the issue/problem: do nothing? add as a work item to an > existing WG? form a new WG? delegate to an IRTF research group? > something else? Do not expect to reach agreement on the solution to > the problem within the time allotted on the Grenoble agenda (though > maybe agreement will be arrived at in the hallways/restaurants/bars > sometime during the three days). > >Any questions, please let us know. > >Steve Deering >Bob Hinden > > >-------------------------------------------------------------------- >IETF IPng Working Group Mailing List >IPng Home Page: http://playground.sun.com/ipng >FTP archive: ftp://playground.sun.com/pub/ipng >Direct all administrative requests to majordomo(a)sunroof.eng.sun.com >-------------------------------------------------------------------- >

1 0

Fw: (IPng 7090) V6 Deployment 3rd Day Final Agenda
by Thomas Trede 27 Jan '99

27 Jan '99

FYI. Regards, Thomas Trede -----Urspr|ngliche Nachricht----- Von: Jim Bound <bound(a)wasted.zk3.dec.com> An: ipng(a)sunroof.Eng.Sun.COM <ipng(a)sunroof.Eng.Sun.COM>; 6bone(a)isi.edu <6bone(a)isi.edu>; ngtrans(a)sunroof.Eng.Sun.COM <ngtrans(a)sunroof.Eng.Sun.COM> Cc: v6-deployment-cabal(a)alpha.zk3.dec.com <v6-deployment-cabal(a)alpha.zk3.dec.com> Datum: Dienstag, 26. Januar 1999 20:39 Betreff: (IPng 7090) V6 Deployment 3rd Day Final Agenda > >=== >Thursday, February 4 -- IPv6 Deployment and Promotion >----------------------------------------------------- >The purpose of this day will be to review current deployment >activities, potential additional efforts, and opportunities for >educating and influencing developers, ISPs, network managers, and >users. This will include answering the following questions: >- Why would anyone run IPv6 now? >- Why would anyone ever run IPv6? >- Who will deploy IPv6 first? >- Will the Internet lead Corporate networks or follow as IPv6 is >deployed? >- How to get ISPs to deploy IPv6? > >We would like to request that each attendee come with answers to the >above questions for discussion on this 3rd day. > >This is the Final Agenda before Grenbole. We will do Agenda Bashing at >Grenoble and select order and times. > >Agenda: >(1) Discussion of the questions above. >(2) Existing deployment efforts: >- 6BONE (who?) >- 6REN (who?) >(3) Potential efforts: >- IPv6 Exchanges (who?) >- Corporate Plans (who?) >- ISP Plans (who?) >- ... >(4) Promotion >- IPv6.org (who?) >- Influencing developers, vendors, etc. (who?) >(5) Presentations: >- Bob Fink - 6REN and 6TAP >- Jim Bound - The Palo Alto Gateway and IPv6 and sub-TLA Request Strategy >- Marc Blanchet - IPv6 Deployment Issues >- Henk Steenman - Amsterdam Internet Exchange (AMS-IX) native IPv6 environment >- Jim Bound for Perry Metzger - Status of the V6 Deployment List Activities >- Jun Murai - IPv6 Deployment in Japan >- Paula Caslav - Proposed Guidelines RIPE NCC Regional Registries for IPv6 >(6) Public Domain Code Needs for IPv6 Discussion >- Appache Web Server >- Sendmail >- BIND >- BSD Network Utilities > >thanks >/jim >-------------------------------------------------------------------- >IETF IPng Working Group Mailing List >IPng Home Page: http://playground.sun.com/ipng >FTP archive: ftp://playground.sun.com/pub/ipng >Direct all administrative requests to majordomo(a)sunroof.eng.sun.com >-------------------------------------------------------------------- >

1 0

Fw: (IPng 7095) Current NGtrans agenda for 2nd day of Grenoble interim meetings
by Thomas Trede 27 Jan '99

27 Jan '99

FYI. Regards, Thomas Trede -----Urspr|ngliche Nachricht----- Von: Bob Fink <fink(a)es.net> An: ngtrans(a)sunroof.Eng.Sun.COM <ngtrans(a)sunroof.Eng.Sun.COM>; IPng List <ipng(a)sunroof.Eng.Sun.COM> Cc: Bob Fink <fink(a)es.net>; Tony Hain <tonyhain(a)microsoft.com> Datum: Mittwoch, 27. Januar 1999 01:52 Betreff: (IPng 7095) Current NGtrans agenda for 2nd day of Grenoble interim meetings >NGtrans Folk, > >Below is the current, and final pre-meeting, NGtrans agenda for the 2nd day >of the Grenoble interim meetings. We can still alter the agenda at the >meeting. > >As Bob and Steve are doing for the IPng interim meeting, we would like to >assign an assignment for attendees, so please read below. > > >Thanks, > >Tony and Bob > >------------------------------------------------------ >Wednesday, February 3 -- NGtrans working group meeting >------------------------------------------------------ > >Purpose: > >The NGtrans working group has developed a large set of transition tools >including the original transition mechanisms (i.e., dual stack w/IPv6 >over IPv4 tunneling), 6over4 without explicit tunnels, translation, >and other tunneling techniques. The purpose of the meeting is for the >working group to converge on a smaller set of tools and mechanisms. >The meeting will include discussing specific transition scenarios and >evaluating how the current transition tools and mechanism work in >these environments. > > >Requirements for Attendees: > >**NOTE** All attendees are required to bring two lists, hopefully each on a >single sheet of paper, as follows: > >1. how you would evaluate the various transition tools/mechanisms under >agenda item (2). > >2. your favorite (i.e., most important) transition scenario to provide for >under agenda item (4). > > >Agenda: > >(1) Review NGtrans mission and charter (brief) - Bob Fink > >(2) Review transition tools/mechanism and how to evaluate them - Jim Bound > with help from various authors as needed (Cyndi Jung, Kazuaki Tsuchiya, >etc.) > >(3) Discuss specific transition scenarios - Tony Hain > with help from various folk (Jim Bound, etc.) > >(4) Evaluate tools/mechanisms against transition scenarios to establish > which to converge on - Bob Fink/Tony Hain > >(5) NGtrans mission and charter reprise (wrapup) - Tony Hain > >-end > > >-------------------------------------------------------------------- >IETF IPng Working Group Mailing List >IPng Home Page: http://playground.sun.com/ipng >FTP archive: ftp://playground.sun.com/pub/ipng >Direct all administrative requests to majordomo(a)sunroof.eng.sun.com >-------------------------------------------------------------------- >

1 0