[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RRG] Meeting slot at IETF64
Hi, Avri Doria
That's great, we really need a meeting to review the current work and dicuss the future work of our group.
I suppose we will get a lot of good ideas and reports from the members.
And if possible, I'd like to make a short report (maybe twenty minutes) to introduce some work we have done and some work we are doing.
Following is the three possible topics of the report.
To solve the problem of BGP4 and to meet the demand of the development of next generation Internet, we propose such modifications to inter-domain routing protocol:
First, hierarchical structure combined with multipath routing, in which hierarchical structure solving scalability and stability problem and multipath satisfying the need of inter-domain routing traffic engineering. Multipath will ease the control of outgoing inter-domain traffic and new mechanism may automatic distribute traffic on multiple routes. Though multipath will add the scale of BGP routing table, more strict hierarchical structure of inter-domain routing will confine the addition to a very small scope.
Second, support for real IP address access. The service of present routing system is forwarding packets with best effort, which do not guarantee the genuineness of the packets. Real IP address access is to assure the received packet is indeed sent form the host with the source IP address in the packet. To provide this service, the routers need to have the additional information to judge whether the packets received is valid or not. Our design is to extend inter-domain routing protocol to provide the information.
Third, mechanism design of inter-domain routing. Mechanism is a concept from Economic used to solve gaming problems. The physical connection and the economic relation among ASes is becoming more and more complicated. We consider to bring mechanism design to inter-domain routing protocol design to restrict the selfish behavior of some ASes, making the interest of ASes consistent with the performance of the Internet perceived by network users.
>I have just requested a meeting slot for Vancouver.
>I request that people who have suggestions for agenda items let me
>know in the near future.
>I am especially interested in
>- Ideas for research that this group should be doing
>- reports on ongoing research that are of interest to the IRTF RRG
>As this is not a WG, contentful reports are welcome, though depending
>on how many people want to report, time may be limited. Though my
>current idea is to prefer a few good substantive issue discussions
>over a succession of overviews.
>As part of the meeting agenda, I will also hold an open discussion on
>what can and should be done to make this group an active force in
>trying to improve Internet Routing. So come with ideas. Please.
>As I know more about the schedule I will let people know. BTW: I
>have requested that this meeting not conflict with other routing
>meetings or other IRTF meetings - we will see if that can be done.
>to unsubscribe send a message to firstname.lastname@example.org with the
>word 'unsubscribe' in a single line as the message text body.
>archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg
to unsubscribe send a message to email@example.com with the
word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg