Adding ChromotingCapability to FTL registration entry

Change-Id: Ifd9e0398c143d5d8e1f9ecbbbdf835646f5e235d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1634396Reviewed-by: Yuwei Huang <yuweih@chromium.org>
Commit-Queue: Joe Downing <joedow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#664415}

remoting/proto/ftl/v1/ftl_messages.proto

@@ -60,6 +60,14 @@ message SignInGaiaMode {
   }
 }
 
+message ChromotingCapability {
+  enum Feature {
+    UNKNOWN = 0;
+    SERIALIZED_XMPP_SIGNALING = 256;
+    WEBRTC_SIGNALING = 257;
+  }
+}
+
 message FtlCapability {
   enum Feature {
     UNKNOWN = 0;

remoting/signaling/ftl_registration_manager.cc

@@ -20,6 +20,13 @@ namespace remoting {
 
 namespace {
 
+constexpr remoting::ftl::ChromotingCapability::Feature
+    kChromotingCapabilities[] = {
+        remoting::ftl::ChromotingCapability_Feature_SERIALIZED_XMPP_SIGNALING};
+constexpr size_t kChromotingCapabilityCount =
+    sizeof(kChromotingCapabilities) /
+    sizeof(ftl::ChromotingCapability::Feature);
+
 constexpr remoting::ftl::FtlCapability::Feature kFtlCapabilities[] = {
     remoting::ftl::FtlCapability_Feature_RECEIVE_CALLS_FROM_GAIA,
     remoting::ftl::FtlCapability_Feature_GAIA_REACHABLE};
@@ -81,6 +88,10 @@ void FtlRegistrationManager::DoSignInGaia(DoneCallback on_done) {
   *request.mutable_register_data()->mutable_device_id() =
       device_id_provider_->GetDeviceId();
 
+  for (size_t i = 0; i < kChromotingCapabilityCount; i++) {
+    request.mutable_register_data()->add_caps(kChromotingCapabilities[i]);
+  }
+
   for (size_t i = 0; i < kFtlCapabilityCount; i++) {
     request.mutable_register_data()->add_caps(kFtlCapabilities[i]);
   }