lisp Discussion Archive - Thread Index

[Prev Page] [Next Page] [Date Index] [IETF Mailing List Directory] [lisp List Information]

• [lisp] Map-Request error, Noel Chiappa
  • Re: [lisp] Map-Request error, Joel M. Halpern
  • Re: [lisp] Map-Request error, Sam Hartman
  • <Possible follow-ups>
  • Re: [lisp] Map-Request error, Noel Chiappa
• [lisp] if you want to connect to the LISP test network..., David Meyer
• [lisp] LISP WG changes after Hiroshima, Jari Arkko
  • Re: [lisp] LISP WG changes after Hiroshima, vijay gill
• [lisp] Agenda for LISP?, Margaret Wasserman
  • Re: [lisp] Agenda for LISP?, Darrel Lewis (darlewis)
• [lisp] Where are the lig sources?, Sam Hartman
  • Re: [lisp] Where are the lig sources?, Sam Hartman
  • Re: [lisp] Where are the lig sources?, David Meyer
    • Re: [lisp] Where are the lig sources?, David Meyer
      • Re: [lisp] Where are the lig sources?, Margaret Wasserman
      • Re: [lisp] Where are the lig sources?, David Meyer
  • <Possible follow-ups>
  • Re: [lisp] Where are the lig sources?, Noel Chiappa
• [lisp] Minute taker and scribe for meeting, Terry Manderson
  • Re: [lisp] Minute taker and scribe for meeting, Terry Manderson
• [lisp] Interest in interop testing Sunday, Sam Hartman
  • Re: [lisp] Interest in interop testing Sunday, Dino Farinacci
    • Re: [lisp] Interest in interop testing Sunday, Margaret Wasserman
    • Re: [lisp] Interest in interop testing Sunday, Sam Hartman
      • Re: [lisp] Interest in interop testing Sunday, Damien Saucez
      • Re: [lisp] Interest in interop testing Sunday, Luigi Iannone
• [lisp] Comments to LISP+ALT draft, Flinck, Hannu (NSN - FI/Espoo)
  • Re: [lisp] Comments to LISP+ALT draft, Vince Fuller
    • Re: [lisp] Comments to LISP+ALT draft, Sam Hartman
• [lisp] Update on moving LISP, Sam Hartman
  • Re: [lisp] Update on moving LISP, Margaret Wasserman
    • Re: [lisp] Update on moving LISP, Darrel Lewis (darlewis)
    • Re: [lisp] Update on moving LISP, Sam Hartman
  • Re: [lisp] Update on moving LISP, Luigi Iannone
    • Re: [lisp] Update on moving LISP, Sam Hartman
      • Re: [lisp] Update on moving LISP, Luigi Iannone
• [lisp] http://tools.ietf.org/wg/lisp/trac/wiki/Security01 with significantly more detail, Sam Hartman
• [lisp] Who is affected by the RRG LISP conflict Friday morning, Sam Hartman
  • Re: [lisp] Who is affected by the RRG LISP conflict Friday morning, Lixia Zhang
  • Re: [lisp] Who is affected by the RRG LISP conflict Friday morning, Eduardo Ascenço Reis
  • Re: [lisp] Who is affected by the RRG LISP conflict Friday morning, Joel M. Halpern
  • Re: [lisp] Who is affected by the RRG LISP conflict Friday morning, Templin, Fred L
• [lisp] Second call for Agenda items, Sam Hartman
• [lisp] Reminder: Upcoming Draft Deadlines, Darrel Lewis (darlewis)
  • [lisp] Requesting time to discuss my proposed security model, Sam Hartman
    • Re: [lisp] Requesting time to discuss my proposed security model, Darrel Lewis (darlewis)
• [lisp] Please read draft-bagnulo-lisp-threat-01.txt, Sam Hartman
• [lisp] FW: LISP - Requested sessions have been scheduled for IETF 76, Darrel Lewis (darlewis)
• [lisp] I-D Action:draft-ietf-lisp-ms-04.txt, Internet-Drafts
• [lisp] updated LISP-MS document - draft-ietf-lisp-ms-04.txt, Vince Fuller
• [lisp] I-D Action:draft-ietf-lisp-ms-03.txt, Internet-Drafts
• [lisp] update to LISP-MS (draft-ietf-lisp-ms-03.txt), Vince Fuller
• [lisp] experimental RFCs, Jari Arkko
• [lisp] I-D Action:draft-ietf-lisp-multicast-02.txt, Internet-Drafts
• [lisp] I-D Action:draft-ietf-lisp-05.txt, Internet-Drafts
• [lisp] Proposed changes to draft-ietf-lisp-multicast-02.txt, Dino Farinacci
• [lisp] Later Monday morning diffs, Dino Farinacci
  • Re: [lisp] Later Monday morning diffs, Darrel Lewis (darlewis)
• [lisp] Early Monday morning diffs, Dino Farinacci
  • Re: [lisp] Early Monday morning diffs, Darrel Lewis (darlewis)
• [lisp] Proposed change to draft-ietf-lisp-05.txt --- 09/26/09 Sat Night, Dino Farinacci
• [lisp] Clarification on issue #16 Map versioning Discussion, Luigi Iannone
  • Re: [lisp] Clarification on issue #16 Map versioning Discussion, Sam Hartman
• [lisp] Proposed change to draft-ietf-lisp-05.txt, Dino Farinacci
  • Re: [lisp] Proposed change to draft-ietf-lisp-05.txt, Margaret Wasserman
    • Re: [lisp] Proposed change to draft-ietf-lisp-05.txt, Dino Farinacci
      • Re: [lisp] Proposed change to draft-ietf-lisp-05.txt, Margaret Wasserman
      • Re: [lisp] Proposed change to draft-ietf-lisp-05.txt, Dino Farinacci
  • <Possible follow-ups>
  • Re: [lisp] Proposed change to draft-ietf-lisp-05.txt, Noel Chiappa
    • Re: [lisp] Proposed change to draft-ietf-lisp-05.txt, Joel M. Halpern
      • Re: [lisp] Proposed change to draft-ietf-lisp-05.txt, Margaret Wasserman
    • Re: [lisp] Proposed change to draft-ietf-lisp-05.txt, Margaret Wasserman
  • Re: [lisp] Proposed change to draft-ietf-lisp-05.txt, Noel Chiappa
    • Re: [lisp] Proposed change to draft-ietf-lisp-05.txt, Margaret Wasserman
      • Re: [lisp] Proposed change to draft-ietf-lisp-05.txt, Dino Farinacci
  • Re: [lisp] Proposed change to draft-ietf-lisp-05.txt, Noel Chiappa
  • Re: [lisp] Proposed change to draft-ietf-lisp-05.txt, Noel Chiappa
    • Re: [lisp] Proposed change to draft-ietf-lisp-05.txt, Margaret Wasserman
      • Re: [lisp] Proposed change to draft-ietf-lisp-05.txt, Margaret Wasserman
• [lisp] Preparing changes for -05, Dino Farinacci
  • Re: [lisp] Preparing changes for -05, Margaret Wasserman
• [lisp] #2: Consensus in favor of replacing IPsec with a MAC, Sam Hartman
• [lisp] #24: Encapsulated control packets on the LISP data port 4341, lisp issue tracker
  • Re: [lisp] #24: Encapsulated control packets on the LISP data port 4341, Sam Hartman
• [lisp] My Position on Vince's Proposal and Issue #22..., Margaret Wasserman
  • Re: [lisp] My Position on Vince's Proposal and Issue #22..., Dino Farinacci
    • Re: [lisp] My Position on Vince's Proposal and Issue #22..., Sam Hartman
  • <Possible follow-ups>
  • Re: [lisp] My Position on Vince's Proposal and Issue #22..., Noel Chiappa
    • Re: [lisp] My Position on Vince's Proposal and Issue #22..., Margaret Wasserman
  • Re: [lisp] My Position on Vince's Proposal and Issue #22..., Noel Chiappa
  • Re: [lisp] My Position on Vince's Proposal and Issue #22..., Noel Chiappa
• [lisp] New Issues: Documents need disclaimers (see Charter), Margaret Wasserman
• [lisp] The other question, Noel Chiappa
  • Re: [lisp] The other question, John Zwiebel
  • Re: [lisp] The other question, Joel M. Halpern
  • <Possible follow-ups>
  • Re: [lisp] The other question, Noel Chiappa
• Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Noel Chiappa
  • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Sam Hartman
    • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Dino Farinacci
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Sam Hartman
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Dino Farinacci
  • <Possible follow-ups>
  • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Noel Chiappa
  • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Noel Chiappa
• [lisp] #23: inner source RLOC undefined in some cases, lisp issue tracker
  • Re: [lisp] #23: inner source RLOC undefined in some cases, Dino Farinacci
    • Re: [lisp] #23: inner source RLOC undefined in some cases, Sam Hartman
      • Re: [lisp] #23: inner source RLOC undefined in some cases, Dino Farinacci
• Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Noel Chiappa
  • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Margaret Wasserman
    • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Margaret Wasserman
  • <Possible follow-ups>
  • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Noel Chiappa
  • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Noel Chiappa
    • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Margaret Wasserman
  • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Noel Chiappa
    • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Joel M. Halpern
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Dino Farinacci
    • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Margaret Wasserman
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, John Zwiebel
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Margaret Wasserman
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Dino Farinacci
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Margaret Wasserman
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Margaret Wasserman
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Dino Farinacci
  • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Noel Chiappa
  • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Noel Chiappa
    • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Sam Hartman
  • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Noel Chiappa
    • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Vince Fuller
• Re: [lisp] #5: protocol version in lisp header, lisp issue tracker
• [lisp] LISP-NAT - explanation and support?, Robin Whittle
  • Re: [lisp] LISP-NAT - explanation and support?, Darrel Lewis (darlewis)
    • Re: [lisp] LISP-NAT - explanation and support?, Robin Whittle
• [lisp] Business models - PITRs, PETRs and EID-rental, Robin Whittle
• [lisp] To IPsec or not IPsec (Issue #2)?, Brian Weis
  • Re: [lisp] To IPsec or not IPsec (Issue #2)?, Dino Farinacci
    • Re: [lisp] To IPsec or not IPsec (Issue #2)?, David Meyer
  • Re: [lisp] To IPsec or not IPsec (Issue #2)?, John Zwiebel
  • Re: [lisp] To IPsec or not IPsec (Issue #2)?, Sam Hartman
  • Re: [lisp] To IPsec or not IPsec (Issue #2)?, Sam Hartman
  • <Possible follow-ups>
  • Re: [lisp] To IPsec or not IPsec (Issue #2)?, Noel Chiappa
• [lisp] Call for interest in working on security, Sam Hartman
  • Re: [lisp] Call for interest in working on security, Eliot Lear
    • Re: [lisp] Call for interest in working on security, Sam Hartman
      • Re: [lisp] Call for interest in working on security, Luigi Iannone
      • Re: [lisp] Call for interest in working on security, Eliot Lear
      • Re: [lisp] Call for interest in working on security, Luigi Iannone
      • Re: [lisp] Call for interest in working on security, Eliot Lear
      • Re: [lisp] Call for interest in working on security, Sam Hartman
      • [lisp] Comments on draft-saucez-lisp-security-00, Sam Hartman
• [lisp] A number of issues I'm not bringing up, Sam Hartman
• [lisp] Jumpstarting discussion on draft-ietf-lisp-05, Darrel Lewis (darlewis)
• [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Darrel Lewis (darlewis)
  • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers (PETRs), Robin Whittle
  • <Possible follow-ups>
  • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Noel Chiappa
    • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Robin Whittle
      • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Darrel Lewis (darlewis)
      • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Sam Hartman
      • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Darrel Lewis (darlewis)
      • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Sam Hartman
      • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Darrel Lewis (darlewis)
      • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, David Meyer
      • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Sam Hartman
      • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, David Meyer
      • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Sam Hartman
      • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, David Meyer
      • [lisp] Mostly pointless argument about V6 transition, Sam Hartman
      • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Jari Arkko
      • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Darrel Lewis (darlewis)
    • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Sam Hartman
      • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Robin Whittle
      • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Joel M. Halpern
      • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Sam Hartman
  • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Noel Chiappa
  • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Noel Chiappa
  • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Noel Chiappa
    • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Sam Hartman
  • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Noel Chiappa
    • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Darrel Lewis (darlewis)
  • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Noel Chiappa
    • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Joel M. Halpern
  • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Noel Chiappa
    • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Joel M. Halpern
  • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Joel M. Halpern
    • Re: [lisp] LISP Interworking: Proxy Egress Tunnel Routers, Dino Farinacci
• [lisp] #22: rough support for fixing MS requires XTRs to consume packets not address to them, Sam Hartman
  • [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Vince Fuller
    • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Sam Hartman
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Sam Hartman
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Dino Farinacci
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Sam Hartman
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Dino Farinacci
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Margaret Wasserman
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Dino Farinacci
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Joel M. Halpern
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Dino Farinacci
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Margaret Wasserman
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Dino Farinacci
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Sam Hartman
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Dino Farinacci
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Margaret Wasserman
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Dino Farinacci
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Joel M. Halpern
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Dino Farinacci
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Joel M. Halpern
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Dino Farinacci
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Vince Fuller
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Joel M. Halpern
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Dino Farinacci
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Sam Hartman
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Dino Farinacci
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Sam Hartman
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Vince Fuller
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Margaret Wasserman
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Margaret Wasserman
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Dino Farinacci
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Margaret Wasserman
      • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Dino Farinacci
    • Re: [lisp] proposed fix issue #22 - processing of Encapsulated Map Requests, Margaret Wasserman
• Re: [lisp] #19: not including the M bit, Noel Chiappa
  • Re: [lisp] #19: not including the M bit, Eliot Lear
    • Re: [lisp] #19: not including the M bit, Jari Arkko
  • [lisp] IANA allocations, Sam Hartman
    • Re: [lisp] IANA allocations, Margaret Wasserman
      • Re: [lisp] IANA allocations, Margaret Wasserman
    • Re: [lisp] IANA allocations, Dino Farinacci
      • Re: [lisp] IANA allocations, Margaret Wasserman
      • Re: [lisp] IANA allocations, Dino Farinacci
      • Re: [lisp] IANA allocations, Brian E Carpenter
  • <Possible follow-ups>
  • Re: [lisp] #19: not including the M bit, Noel Chiappa
    • Re: [lisp] #19: not including the M bit, Sam Hartman
• [lisp] #16: map versioning/data plane consensus call, Sam Hartman
  • Re: [lisp] #16: map versioning/data plane consensus call, Luigi Iannone
  • <Possible follow-ups>
  • Re: [lisp] #16: map versioning/data plane consensus call, Noel Chiappa
• [lisp] #5: LISP protocol version is alive and kicking, Sam Hartman
  • Re: [lisp] #5: LISP protocol version is alive and kicking, Damien Saucez
    • Re: [lisp] #5: LISP protocol version is alive and kicking, Dino Farinacci
      • Re: [lisp] #5: LISP protocol version is alive and kicking, Damien Saucez
      • Re: [lisp] #5: LISP protocol version is alive and kicking, Dino Farinacci
      • Re: [lisp] #5: LISP protocol version is alive and kicking, Dino Farinacci
      • Re: [lisp] #5: LISP protocol version is alive and kicking, Damien Saucez
    • Re: [lisp] #5: LISP protocol version is alive and kicking, Joel M. Halpern
      • Re: [lisp] #5: LISP protocol version is alive and kicking, Damien Saucez
      • Re: [lisp] #5: LISP protocol version is alive and kicking, Dino Farinacci
      • Re: [lisp] #5: LISP protocol version is alive and kicking, Sam Hartman
      • Re: [lisp] #5: LISP protocol version is alive and kicking, Damien Saucez
  • <Possible follow-ups>
  • Re: [lisp] #5: LISP protocol version is alive and kicking, Noel Chiappa
  • Re: [lisp] #5: LISP protocol version is alive and kicking, Noel Chiappa
    • Re: [lisp] #5: LISP protocol version is alive and kicking, Darrel Lewis (darlewis)
      • Re: [lisp] #5: LISP protocol version is alive and kicking, Sam Hartman
      • Re: [lisp] #5: LISP protocol version is alive and kicking, Darrel Lewis (darlewis)
      • Re: [lisp] #5: LISP protocol version is alive and kicking, Sam Hartman
      • Re: [lisp] #5: LISP protocol version is alive and kicking, Darrel Lewis (darlewis)
  • Re: [lisp] #5: LISP protocol version is alive and kicking, Noel Chiappa
    • Re: [lisp] #5: LISP protocol version is alive and kicking, Darrel Lewis (darlewis)
  • Re: [lisp] #5: LISP protocol version is alive and kicking, Noel Chiappa
  • Re: [lisp] #5: LISP protocol version is alive and kicking, Terry Manderson
  • Re: [lisp] #5: LISP protocol version is alive and kicking, Noel Chiappa
    • Re: [lisp] #5: LISP protocol version is alive and kicking, Terry Manderson
• [lisp] I-D Action:draft-ietf-lisp-04.txt, Internet-Drafts
• [lisp] #9, #10, #11: UDP checksum consensus call, Sam Hartman
  • Re: [lisp] #9, #10, #11: UDP checksum consensus call, Dino Farinacci
• [lisp] LISP Over Lossy Links, Margaret Wasserman
  • Re: [lisp] LISP Over Lossy Links, Margaret Wasserman
  • Re: [lisp] LISP Over Lossy Links, Dino Farinacci
    • Re: [lisp] LISP Over Lossy Links, Margaret Wasserman
      • Re: [lisp] LISP Over Lossy Links, Loránd Jakab
      • Re: [lisp] LISP Over Lossy Links, Margaret Wasserman
      • Re: [lisp] LISP Over Lossy Links, Joel M. Halpern
      • Re: [lisp] LISP Over Lossy Links, Damien Saucez
      • Re: [lisp] LISP Over Lossy Links, John Zwiebel
      • Re: [lisp] LISP Over Lossy Links, Marshall Eubanks
      • Re: [lisp] LISP Over Lossy Links, Jesper Skriver
    • Re: [lisp] LISP Over Lossy Links, Loránd Jakab
      • Re: [lisp] LISP Over Lossy Links, Marshall Eubanks
      • Re: [lisp] LISP Over Lossy Links, Eliot Lear
      • Re: [lisp] LISP Over Lossy Links, Margaret Wasserman
      • Re: [lisp] LISP Over Lossy Links, Eliot Lear
    • Re: [lisp] LISP Over Lossy Links, Damien Saucez
    • Re: [lisp] LISP Over Lossy Links, Florin Coras
      • Re: [lisp] LISP Over Lossy Links, Dino Farinacci
  • <Possible follow-ups>
  • Re: [lisp] LISP Over Lossy Links, Noel Chiappa
  • Re: [lisp] LISP Over Lossy Links, Noel Chiappa
    • Re: [lisp] LISP Over Lossy Links, Margaret Wasserman
      • Re: [lisp] LISP Over Lossy Links, Sam Hartman
    • Re: [lisp] LISP Over Lossy Links, Margaret Wasserman
  • Re: [lisp] LISP Over Lossy Links, Noel Chiappa
  • Re: [lisp] LISP Over Lossy Links, Noel Chiappa
  • Re: [lisp] LISP Over Lossy Links, Noel Chiappa
• Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Noel Chiappa
  • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Margaret Wasserman
  • <Possible follow-ups>
  • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Noel Chiappa
    • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Margaret Wasserman
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Margaret Wasserman
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Joel M. Halpern
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Dino Farinacci
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Margaret Wasserman
    • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Margaret Wasserman
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1MTU Handling, Templin, Fred L
  • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Noel Chiappa
    • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Margaret Wasserman
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Dino Farinacci
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Sam Hartman
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, John Zwiebel
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Dino Farinacci
  • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Noel Chiappa
  • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Noel Chiappa
• [lisp] #20: supporting SMR bit only in control plane, Sam Hartman
  • Re: [lisp] #20 consensus call: SMR bit in control plane only, Sam Hartman
• [lisp] I am not posting the -04 document today, Dino Farinacci
  • Re: [lisp] I am not posting the -04 document today, Sam Hartman
    • Re: [lisp] I am not posting the -04 document today, Dino Farinacci
      • Re: [lisp] I am not posting the -04 document today, Luigi Iannone
      • Re: [lisp] I am not posting the -04 document today, Margaret Wasserman
      • Re: [lisp] I am not posting the -04 document today, John Zwiebel
      • [lisp] #19: not including the M bit, Sam Hartman
      • Re: [lisp] #19: not including the M bit, Jari Arkko
      • Re: [lisp] #19: not including the M bit, Dino Farinacci
      • Re: [lisp] #19: not including the M bit, Sam Hartman
  • <Possible follow-ups>
  • Re: [lisp] I am not posting the -04 document today, Noel Chiappa
    • Re: [lisp] I am not posting the -04 document today, John Zwiebel
• [lisp] Any objections for posting draft-ietf-lisp-04.txt?, Dino Farinacci
  • [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Margaret Wasserman
    • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Templin, Fred L
    • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Sam Hartman
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Margaret Wasserman
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Marshall Eubanks
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Margaret Wasserman
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Marshall Eubanks
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Margaret Wasserman
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Joel M. Halpern
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Margaret Wasserman
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Joel M. Halpern
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Margaret Wasserman
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Magnus Westerlund
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Joel M. Halpern
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Magnus Westerlund
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Joel M. Halpern
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Magnus Westerlund
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Margaret Wasserman
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Marshall Eubanks
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Margaret Wasserman
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Margaret Wasserman
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Loránd Jakab
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Joel M. Halpern
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTU Handling, Magnus Westerlund
      • Re: [lisp] New Issue: UDP-TUNNELS inconsistent with 5.4.1 MTUHandling, Templin, Fred L
• [lisp] Consensus Call: 64-bit nonce and randomness of nonce, Sam Hartman
• [lisp] Thursday updated diff file for the lisp-04 proposed changes, Dino Farinacci
• [lisp] Wednesday updated diff file for the lisp-04 proposed changes, Dino Farinacci
  • Re: [lisp] Wednesday updated diff file for the lisp-04 proposed changes, Marshall Eubanks
    • Re: [lisp] Wednesday updated diff file for the lisp-04 proposed changes, Dino Farinacci
• [lisp] We have converged on 64 bits!, Dino Farinacci
  • Re: [lisp] We have converged on 64 bits!, Margaret Wasserman
• Re: [lisp] 32-bit nonce in map request insufficient, Noel Chiappa
• [lisp] Packet format change mechanism [Was: #8: Limits on "Gleaned" Map Entries Not Clear], Noel Chiappa
  • Re: [lisp] Packet format change mechanism [Was: #8: Limits on "Gleaned" Map Entries Not Clear], Sam Hartman
• [lisp] Tuesday updated diff file for the lisp-04 proposed changes, Dino Farinacci
• [lisp] Updated text to data gleaning, Dino Farinacci
• [lisp] Lisp WG concerns, Jari Arkko
• Re: [lisp] #8: Limits on "Gleaned" Map Entries Not Clear, Noel Chiappa
  • <Possible follow-ups>
  • Re: [lisp] #8: Limits on "Gleaned" Map Entries Not Clear, Noel Chiappa
    • Re: [lisp] #8: Limits on "Gleaned" Map Entries Not Clear, Dino Farinacci
      • Re: [lisp] #8: Limits on "Gleaned" Map Entries Not Clear, Sam Hartman
    • [lisp] 32-bit nonce in map request insufficient, Sam Hartman
      • Re: [lisp] 32-bit nonce in map request insufficient, Darrel Lewis (darlewis)
      • Re: [lisp] 32-bit nonce in map request insufficient, Sam Hartman
      • Re: [lisp] 32-bit nonce in map request insufficient, Margaret Wasserman
      • Re: [lisp] 32-bit nonce in map request insufficient, Darrel Lewis (darlewis)
      • Re: [lisp] 32-bit nonce in map request insufficient, Margaret Wasserman
      • Re: [lisp] 32-bit nonce in map request insufficient, Darrel Lewis (darlewis)
      • Re: [lisp] 32-bit nonce in map request insufficient, Joel M. Halpern
      • Re: [lisp] 32-bit nonce in map request insufficient, Darrel Lewis (darlewis)
      • Re: [lisp] 32-bit nonce in map request insufficient, Margaret Wasserman
      • Re: [lisp] 32-bit nonce in map request insufficient, Margaret Wasserman
      • Re: [lisp] 32-bit nonce in map request insufficient, Christopher Morrow
      • Re: [lisp] 32-bit nonce in map request insufficient, Margaret Wasserman
      • Re: [lisp] 32-bit nonce in map request insufficient, Christopher Morrow
      • Re: [lisp] 32-bit nonce in map request insufficient, Dino Farinacci
      • Re: [lisp] 32-bit nonce in map request insufficient, Joel M. Halpern
      • Re: [lisp] 32-bit nonce in map request insufficient, Margaret Wasserman
      • Re: [lisp] 32-bit nonce in map request insufficient, Christopher Morrow
      • Re: [lisp] 32-bit nonce in map request insufficient, Dino Farinacci
      • Re: [lisp] 32-bit nonce in map request insufficient, Margaret Wasserman
      • [lisp] text suggestion for random nonces, Sam Hartman
      • Re: [lisp] text suggestion for random nonces, Margaret Wasserman
      • Re: [lisp] text suggestion for random nonces, Sam Hartman
      • Re: [lisp] text suggestion for random nonces, Eliot Lear
      • Re: [lisp] text suggestion for random nonces, Dino Farinacci
      • Re: [lisp] text suggestion for random nonces, Dino Farinacci
      • Re: [lisp] text suggestion for random nonces, Marshall Eubanks
      • Re: [lisp] text suggestion for random nonces, Dino Farinacci
      • [lisp] Randomness Requirements for Nonce, Margaret Wasserman
      • Re: [lisp] Randomness Requirements for Nonce, Christopher Morrow
  • Re: [lisp] #8: Limits on "Gleaned" Map Entries Not Clear, Noel Chiappa
    • Re: [lisp] #8: Limits on "Gleaned" Map Entries Not Clear, Margaret Wasserman
  • Re: [lisp] #8: Limits on "Gleaned" Map Entries Not Clear, Noel Chiappa
  • Re: [lisp] #8: Limits on "Gleaned" Map Entries Not Clear, Noel Chiappa
    • Re: [lisp] #8: Limits on "Gleaned" Map Entries Not Clear, Margaret Wasserman
  • Re: [lisp] #8: Limits on "Gleaned" Map Entries Not Clear, Noel Chiappa
    • Re: [lisp] #8: Limits on "Gleaned" Map Entries Not Clear, Margaret Wasserman
• [lisp] #22: An ETR MUST consume UDP port 4342 packets not addressed to it, lisp issue tracker
  • Re: [lisp] #22: An ETR MUST consume UDP port 4342 packets not addressed to it, Joel M. Halpern
    • Re: [lisp] #22: An ETR MUST consume UDP port 4342 packets not addressed to it, Dino Farinacci
      • Re: [lisp] #22: An ETR MUST consume UDP port 4342 packets not addressed to it, Joel M. Halpern
      • Re: [lisp] #22: An ETR MUST consume UDP port 4342 packets not addressed to it, Margaret Wasserman
      • Re: [lisp] #22: An ETR MUST consume UDP port 4342 packets not addressed to it, Dino Farinacci
      • Re: [lisp] #22: An ETR MUST consume UDP port 4342 packets not addressed to it, Joel M. Halpern
      • Re: [lisp] #22: An ETR MUST consume UDP port 4342 packets not addressed to it, Dino Farinacci
• [lisp] #21: Section 5.1 behavior, lisp issue tracker
• [lisp] Confirming Consensus on RLOC probing, Sam Hartman
  • Re: [lisp] Confirming Consensus on RLOC probing, Dino Farinacci
  • Re: [lisp] Confirming Consensus on RLOC probing, Sam Hartman
    • Re: [lisp] Confirming Consensus on RLOC probing, Dino Farinacci
      • Re: [lisp] Confirming Consensus on RLOC probing, Sam Hartman
      • Re: [lisp] Confirming Consensus on RLOC probing, Dino Farinacci
  • Re: [lisp] Confirming Consensus on RLOC probing, Jari Arkko
• [lisp] #20: SMR bit only in control plane, lisp issue tracker
• [lisp] #19: mobility bit in map reply, lisp issue tracker
  • Re: [lisp] #19: mobility bit in map reply, Eliot Lear
    • Re: [lisp] #19: mobility bit in map reply, Margaret Wasserman
      • Re: [lisp] #19: mobility bit in map reply, Dino Farinacci
      • Re: [lisp] #19: mobility bit in map reply, Eliot Lear
      • Re: [lisp] #19: mobility bit in map reply, Joel M. Halpern
      • Re: [lisp] #19: mobility bit in map reply, Dino Farinacci
• [lisp] Apologies in advance for the form of some issues I'm opening, Sam Hartman
• [lisp] #18: record count >1 for map request, lisp issue tracker
  • Re: [lisp] #18: record count >1 for map request, Joel M. Halpern
    • Re: [lisp] #18: record count >1 for map request, Dino Farinacci
    • Re: [lisp] #18: record count >1 for map request, Sam Hartman
  • Re: [lisp] #18: record count >1 for map request, Margaret Wasserman
    • Re: [lisp] #18: record count >1 for map request, Joel M. Halpern
    • Re: [lisp] #18: record count >1 for map request, Dino Farinacci
      • Re: [lisp] #18: record count >1 for map request, Margaret Wasserman
      • Re: [lisp] #18: record count >1 for map request, Dino Farinacci
      • Re: [lisp] #18: record count >1 for map request, Dino Farinacci
      • Re: [lisp] #18: record count >1 for map request, Margaret Wasserman
      • Re: [lisp] #18: record count >1 for map request, Dino Farinacci
• [lisp] I-D Action:draft-ietf-lisp-ms-02.txt, Internet-Drafts
• [lisp] [idsubmission at ietf.org: New Version Notification for draft-ietf-lisp-ms-02], Vince Fuller
• [lisp] #2: changes to sha-1 and RFC 4302, Sam Hartman
  • Re: [lisp] #2: changes to sha-1 and RFC 4302, Dino Farinacci
• [lisp] Status of Security work, Sam Hartman
  • Re: [lisp] Status of Security work, Luigi Iannone
• [lisp] Soliciting editors for a document on LISP deployment, Sam Hartman
• [lisp] Confirming consensus behind echo noncing, Sam Hartman
  • Re: [lisp] Confirming consensus behind echo noncing, Sam Hartman
    • Re: [lisp] Confirming consensus behind echo noncing, Dino Farinacci
  • <Possible follow-ups>
  • Re: [lisp] Confirming consensus behind echo noncing, Noel Chiappa
  • Re: [lisp] Confirming consensus behind echo noncing, Noel Chiappa
• [lisp] lisp-04 spec and lisp-ms-02 draft, Dino Farinacci
• [lisp] [#16]: Desire to expand data plane for map versioning or handle in the control plane, Sam Hartman
  • Re: [lisp] [#16]: Desire to expand data plane for map versioning or handle in the control plane, Margaret Wasserman
  • Re: [lisp] [#16]: Desire to expand data plane for map versioning orhandle in the control plane, Darrel Lewis (darlewis)
  • <Possible follow-ups>
  • Re: [lisp] [#16]: Desire to expand data plane for map versioning or handle in the control plane, Noel Chiappa
  • Re: [lisp] [#16]: Desire to expand data plane for map versioning or handle in the control plane, Noel Chiappa
    • Re: [lisp] [#16]: Desire to expand data plane for map versioning or handle in the control plane, Luigi Iannone
    • Re: [lisp] [#16]: Desire to expand data plane for map versioning or handle in the control plane, Damien Saucez
• [lisp] #17: Data plane request for control-plane reply, lisp issue tracker
• [lisp] IETF 75 audio pointer, Sam Hartman
• [lisp] Revised proposed diffs for the -04 LISP draft, Dino Farinacci
• [lisp] To help converge on the UDP checksum text proposed for -04, Dino Farinacci
• [lisp] Please review section 9: traceroute behavior, Sam Hartman
  • Re: [lisp] Please review section 9: traceroute behavior, Dino Farinacci
• Re: [lisp] Suggested UDP checksum text, Noel Chiappa
  • Re: [lisp] Suggested UDP checksum text, Sam Hartman
  • <Possible follow-ups>
  • Re: [lisp] Suggested UDP checksum text, Noel Chiappa
    • Re: [lisp] Suggested UDP checksum text, Dino Farinacci
      • Re: [lisp] Suggested UDP checksum text, Marshall Eubanks
      • Re: [lisp] Suggested UDP checksum text, David Meyer
      • Re: [lisp] Suggested UDP checksum text, Sam Hartman
    • Re: [lisp] Suggested UDP checksum text, Margaret Wasserman
  • Re: [lisp] Suggested UDP checksum text, Noel Chiappa
    • Re: [lisp] Suggested UDP checksum text, Margaret Wasserman
  • Re: [lisp] Suggested UDP checksum text, Noel Chiappa
    • Re: [lisp] Suggested UDP checksum text, Jari Arkko
    • Re: [lisp] Suggested UDP checksum text, Margaret Wasserman
• Re: [lisp] Meanign of R bit, Noel Chiappa
  • Re: [lisp] Meanign of R bit, Joel M. Halpern
  • <Possible follow-ups>
  • Re: [lisp] Meanign of R bit, Noel Chiappa
    • Re: [lisp] Meanign of R bit, Joel M. Halpern
      • Re: [lisp] Meanign of R bit, Sam Hartman
  • Re: [lisp] Meanign of R bit, Noel Chiappa
    • Re: [lisp] Meanign of R bit, Margaret Wasserman
      • Re: [lisp] Meanign of R bit, Margaret Wasserman
• [lisp] Changes proposed to draft-ietf-lisp-ms-02.txt, Dino Farinacci
• [lisp] Deadline for proposed changes to draft-ietf-lisp-04.txt is Friday Sep 4th, Dino Farinacci
  • Re: [lisp] Deadline for proposed changes to draft-ietf-lisp-04.txt is Friday Sep 4th, Sam Hartman
    • Re: [lisp] Deadline for proposed changes to draft-ietf-lisp-04.txt is Friday Sep 4th, Dino Farinacci
      • Re: [lisp] Deadline for proposed changes to draft-ietf-lisp-04.txt is Friday Sep 4th, Sam Hartman
  • Re: [lisp] Suggested UDP checksum text, Joel M. Halpern
    • Re: [lisp] Suggested UDP checksum text, Dino Farinacci
      • Re: [lisp] Suggested UDP checksum text, Margaret Wasserman
      • Re: [lisp] Suggested UDP checksum text, Sam Hartman
      • Re: [lisp] Suggested UDP checksum text, Margaret Wasserman
      • Re: [lisp] Suggested UDP checksum text, Dino Farinacci
      • Re: [lisp] Suggested UDP checksum text, Sam Hartman
      • Re: [lisp] Suggested UDP checksum text, Margaret Wasserman
      • Re: [lisp] Suggested UDP checksum text, Dino Farinacci
      • Re: [lisp] Suggested UDP checksum text, Joel M. Halpern
      • Re: [lisp] Suggested UDP checksum text, Margaret Wasserman
      • Re: [lisp] Suggested UDP checksum text, Marshall Eubanks
      • Re: [lisp] Suggested UDP checksum text, Dino Farinacci