6tsch webex
DESCRIPTION
6TSCH Webex. 05/03/2013. Agenda. update charter: security paragraph[5min] link / peering management[10min] 6TUS building blocks[10min] Centralized routing building blocks[10min] distributed routing building blocks[10min] Wireless ND[10min]. update charter. security paragraph. - PowerPoint PPT PresentationTRANSCRIPT
6TSCH Webex
05/03/2013
Agenda
• update charter: security paragraph [5min]
• link / peering management [10min]
• 6TUS building blocks [10min]
• Centralized routing building blocks [10min]
• distributed routing building blocks [10min]
• Wireless ND [10min]
update charter
security paragraph
New security paragraph
“A document on the security architecture and requirements for 6TSCH will be developed, and depending on the security requirements identified in the document, the group may work on a security solution and ask for security area review.”
was:
“The need for other documents may arise as the group progresses. Informational documents on the security, and in particular the use of PANA for 6TSCH are to be expected and fall within charter.”
Architecture blocks
---+------------------------ | External Network | +-----+ +-----+ | | Router | | PCE / | | | | Common Net Mgt +-----+ +-----+ | | | Subnet Backbone | +--------------------+------------------+ | | | +-----+ +-----+ +-----+ | | Backbone | | Backbone | | Backbone o | | router | | router | | router +-----+ +-----+ +-----+ o o o o o o o o o o o o o o o o o o o LLN o o o o o o o o o o o o o o o o
+-----+-----+-----+-----+-------+-----+ |PCEP | CoAP |PANA | WiND /| RPL | | |DTLS | | | 6LPND | | +-----+-----+-----+-----+-------+-----+-----+ | TCP | UDP | ICMP |RSVP | +-----+-----+-----+-----+-------+-----+-----+ | IPv6 | +-------------------------------------------+ | (6LoWPAN HC) | +-------------------------------------------+ | 6TUS | +-----------------------+--------+----------+ | (802.15.4e) TSCH | | | +-----------+-----------+ DECT | 4G / LTE | | 802.15.4 | 802.11ac | | | +-----------+-----------+--------+----------+
Link / peering mgt
subBlocks• Peer selection
– For PCE, need additional peers left/right
• Peer maintenance– Bidir reachability– Metrics evaluation
6TUS
subBlocks• Scheduler
– Handles 6LoWPAN packets or fragments– Selects xmit slot based on schedule or priority
• GMPLS layer– Switches along a track– Punts at the end of track– Punts untracked packets
• Slot negotiation protocol– With peer 6TUS
Centralized routing
subBlocks• Route Computation engine in PCE
– Out of scope?
• Protocol to request a computation– PCEP? – What about maintainance and destroy?
• Protocol to advertise peerings and metrics– Between PCC and PCE– Reuse RFC 6551 metrics ?
• Protocol to validate a track (OAM)
---+---------------------- | External Network | +-----+ +-----+ | | Router | | PCE/ | | | | NME +-----+ +-----+ | | | Subnet backbone | +--------------------+------------------+ | | | +-----+(RPL root) +-----+(RPL root) +-----+ | | Backbone | | Backbone | | Backbone | | router | | router | | router +-----+ +-----+ +-----+ o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Installing tracks (V1)
The PCE pushesTracks as slot switching (G-MPLS)
SwitchingTable entry
---+---------------------- | External Network | +-----+ +-----+ | | Router | | PCE/ | | | | NME +-----+ +-----+ | | | Subnet backbone | +--------------------+------------------+ | | | +-----+(RPL root) +-----+(RPL root) +-----+ | | Backbone | | Backbone | | Backbone | | router | | router | | router +-----+ +-----+ +-----+ o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Installing tracks (V2)
The PCE pushesTracks as source routing info to requester
SwitchingTable entry
---+---------------------- | External Network | +-----+ +-----+ | | Router | | PCE/ | | | | NME +-----+ +-----+ | | | Subnet backbone | +--------------------+------------------+ | | | +-----+(RPL root) +-----+(RPL root) +-----+ | | Backbone | | Backbone | | Backbone | | router | | router | | router +-----+ +-----+ +-----+ o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
validating tracks(Operations, Administration, and Maintenance)
OAM frames arePeriodically sent along a track to measure metrics
OAM framesSee http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview
Notes on PCEP
Status
• RFC5440
• March 2009
• JP Vasseur, JL. Le Roux, Eds.
• Path Computation Element (PCE) Communication Protocol (PCEP)
Scope
• Communication between– PCE (Path Computation Element)– PCC (Path Computation Client)
• PCC asks for the computation of a path to the PCE, which answers with a PCResp
• Does not define how PCE calculates the path
• Does not define how PCE knows about the network
Communication
• TCP port 4189
• Long-term TCP session, or new TCP session per PCEP transaction.
• Long-term PCEP sessions between PCC and one or more PCC
• Keep-alive mechanism as part of PCEP
Packet Types
1. Open
2. Keepalive
3. PCRequest
4. PCReply
5. Notification
6. Error
7. Close
Remarks/Questions
• (Looks like) TCP can be replaced by CoAP / UDP
• Apply Trickle timer to PCEP keepalives?
• PCEP invoked after the resource have been allocated
• PCNtf to contain topological information?
• Authentication?
• RPL root as relay agent?
Distributed routing
subBlocks
• RPL (as is?)
• OF (?)
• Reservation along a routing path
Initial time ---+---------------------- | External Network | +-----+ +-----+ | | Router | | PCE/ | | | | NME +-----+ +-----+ | | | Subnet backbone | +--------------------+------------------+ | | | +-----+ (root) +-----+ (6LBR) +-----+ | | Backbone | | Backbone | | Backbone | | router | | router | | router +-----+ +-----+ +-----+ o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
---+---------------------- | External Network | +-----+ +-----+ | | Router | | PCE/ | | | | NME +-----+ +-----+ | | | Subnet backbone | +--------------------+------------------+ | | | +-----+ +-----+ +-----+ | | Backbone | | Backbone | | Backbone | | router | | router | | router +-----+ +-----+ +-----+ o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Installing /64 routeA single subnet model for the backbone and thewireless sensor networks
SubnetRouteIn RIB
SubnetRouteIn RIB
SubnetRouteIn RIB
SubnetRouteIn RIB
DefaultRouteIn RIB
SubnetRouteIn RIB
---+---------------------- | External Network | +-----+ +-----+ | | Router | | PCE/ | | | | NME +-----+ +-----+ | | | Subnet backbone | +--------------------+------------------+ | | | +-----+(RPL root) +-----+(RPL root) +-----+ | | Backbone | | Backbone | | Backbone | | router | | router | | router +-----+ +-----+ +-----+ o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Installing /128 routes
The BR maintains a route to the WSN node for the DAOLifetime over instance VRF
DAO DAO
HostRouteIn RIB
HostRouteIn RIB
defaultRouteIn RIB
---+---------------------- | External Network | +-----+ +-----+ | | Router | | PCE/ | | | | NME +-----+ +-----+ | | | Subnet backbone | +--------------------+------------------+ | | | +-----+(RPL root) +-----+(RPL root) +-----+ | | Backbone | | Backbone | | Backbone | | router | | router | | router +-----+ +-----+ +-----+ o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Reservations
Within a DODAGthrough the common parent
RSVPSwitchingTable entry
RSVP / NSIS
• supported on UDP• reservation (Point to Point)• maintenance - status collection and monitorin• Ad-hoc QoS content definition following a TLV and
being appended to a generic header• upstream and downstream reservation• In case of NSIS neighbour discovery in case no
routing state is installed.• hop by hop state installation, does not require end
to end messaging per hop
WiND
Wireless ND
subBlocks
• Registration and DAD – extending 6LoWPAN ND opn the backbone
• Resolution– Distributed through proxy-ND– Or routing in not-onlink mode
---+---------------------- | External Network | +-----+ +-----+ | | Router | | PCE/ | | | | NME +-----+ +-----+ | | | Subnet backbone | +--------------------+------------------+ | | | +-----+ (6LBR) +-----+ (6LBR) +-----+ | | Backbone | | Backbone | | Backbone | | router | | router | | router +-----+ +-----+ +-----+ o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Registration (1st step)
NS(ARO)
DAR
DAD DAD
Registration has:•Lifetime•Unique ID•TID (SeqNum)
---+---------------------- | External Network | +-----+ +-----+ | | Router | | PCE/ | | | | NME +-----+ +-----+ | | | Subnet backbone | +--------------------+------------------+ | | | +-----+ (6LBR) +-----+ (6LBR) +-----+ | | Backbone | | Backbone | | Backbone | | router | | router | | router +-----+ +-----+ +-----+ o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Registration (2nd step one second later)
NA (ARO)
DAC
Opt NA(O)
The BR maintains a binding state to the WSN node for the registration lifetime
Opt NA(O)
---+---------------------- | External Network | +-----+ +-----+ | | Router | | PCE/ | | | | NME +-----+ +-----+ | | | Subnet backbone | +--------------------+------------------+ | | | +-----+ (root) +-----+ (6LBR) +-----+ | | Backbone | | Backbone | | Backbone | | router | | router | | router +-----+ +-----+ +-----+ o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Duplication
DAR
DAC(KO)
DAD NA
DAD option has:•Unique ID•TID (SeqNum)
Defend with NA if:•Different OUID•Newer TID
---+---------------------- | External Network | +-----+ +-----+ | | Router | | PCE/ | | | | NME +-----+ +-----+ | | | Subnet backbone | +--------------------+------------------+ | | | +-----+ +-----+ +-----+ | | Backbone | | Backbone | | Backbone | | router | | router | | router +-----+ +-----+ +-----+ o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Mobility
DAR
DAC (OK)
DAD NA
DAD option has:•Unique ID•TID (SeqNum)
Defend with NA if:•Different OUID•Newer TID
---+---------------------- | External Network | +-----+ +-----+ | | Router | | PCE/ | | | | NME +-----+ +-----+ | | | Subnet backbone | +--------------------+------------------+ | | | +-----+ +-----+ +-----+ | | Backbone | | Backbone | | Backbone | | router | | router | | router +-----+ +-----+ +-----+ o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Resolution
packet
NSNA
NA option has:•Unique ID•TID (SeqNum)
---+---------------------- | External Network | +-----+ +-----+ | | Router | | PCE/ | | | | NME +-----+ +-----+ | | | Subnet backbone | +--------------------+------------------+ | | | +-----+ +-----+ +-----+ | | Backbone | | Backbone | | Backbone | | router | | router | | router +-----+ +-----+ +-----+ o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o o
Resolution (2)
packet
NA
NS