And to Linda's original point, which was about "multiple administrative domains", an appreciation of the Autonomous System (AS) structure of the Internet would certainly be helpful in working with both Routing and Operations folks, but that in no way requires serious knowledge of how BGP works.
Thanks, --David > -----Original Message----- > From: tsv-area [mailto:[email protected]] On Behalf Of > [email protected] > Sent: Saturday, May 30, 2015 5:36 AM > To: John Leslie > Cc: [email protected] > Subject: Re: FYI draft text desired expertise TSV AD (NOMCOM 2015 cycle) > > > I agree, to me BGP isn't a protocol that needs to be understood by a TSV > AD. Like many protocols from other areas, it is one where we need to be > aware of issues so that other groups can determine whether something needs > to be done. > > Gorry > > > Linda Dunbar <[email protected]> wrote: > >> > >> Today's network is layers of layers of overlay (multiple layers of > >> encapsulation). A communication between two end points traverses > >> multiple administrative domains. > > > > Quite true. > > > >> The TSV-Area AD should have the knowledge of BGP, the domain > >> demarcation across different administrative domains. > > > > It's hard enough to find Routing ADs that understand BGP. To repeat > > myself and others: We must make it possible for the NomCom to do its > > job. > > > > TSV ADs should know how to talk to routing experts; but I see no > > reason for them to be BGP experts themselves. > > > > Indeed, even if we consider what happens to packets as they cross > > Administrative Domains to be in-scope for Transport documents (alas, > > sometimes it is), that doesn't mean TSV ADs need to understand the > > details of that issue. > > > > Also, please note that our TSV ADs are seriously trying to organize > > the work so that they don't need to review all documents themselves. > > > > -- > > John Leslie <[email protected]> > > >
